This is fine:
www.bagelconcertfinder.com/zipcodes/{zipCode}

Preferred is :
https://......siteName.../boundedContext/resourceInPlural/{resourceId}

So this can be as you state but without _ underscores and "concertBlogging" is identified bounded context for a set of resources
https://....siteName../concertBlogging/blogs/{blogId}

Plurals are recommended. Lots of Style conformance is recommended, stick to REST and not use actions/ verbs in urls et als..
You can break many of the so called rules and still it will work fine for you, but its up��to you, to decide what you adhere to and what you define for yourself

https://restfulapi.net/resource-naming/��
https://docs.microsoft.com/en-us/azure/architecture/best-practices/api-design

Given the conflicting advices on REST, you can try and adhere to one-two sources of advice.




On Mon, Feb 25, 2019 at 12:13 PM sergio ruiz <sergio.rrd@gmail.com> wrote:
Hi, all..

I am looking to have a repeatable url so users can save them and share them.. something like:

www.bagelconcertfinder.com/zipcode/44805

and in my next project, I���ll be doing something like a CMS where you would get:

/blog_entries/this-is-the-path

I am thinking of using REST to flesh out the paths..

does this seem reasonable?

----
peace,
sergio
photographer, journalist, visionary

Public Key:��http://bit.ly/29z9fG0
#BitMessage��BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV
http://www.codeandmusic.com
http://www.twitter.com/sergio_101
http://www.facebook.com/sergio101