Home/ Questions/Q 888935
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-15T13:29:07+00:00

When you design URL schema for your application, which rules you use? example.com/post/ or

  • 0

When you design URL schema for your application, which rules you use?

  • example.com/post/ or example.com/posts/ for list of posts
  • example.com/post/new/ or example.com/post/create/ for new post
  • example.com/posts/ + example.com/post/23/ or example.com/post/ + example.com/post/23/ for list and detail of post?
  • example.com/post/23 or example.com/post/23/ for details
  • example.com/post/edit/23/ or example.com/post/23/edit/ for editing.

I’m prefered: /post/ for list, /post/23/ for details, /post/23/edit/ for editing, just b/c I’m can very easy work with that URL by hand in browser location bar. I’m wrong? Suggest me, please.

Thanks.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You should probably use the HTTP POST method when creating a new resource. So, for a new customer, you might POST to example.com/customer. Then if you want information on that customer, do a GET to example.com/customer/{your recently created customer id}. If you want all customers, do a GET to example.com/customer If you want to edit a customer you’ll probably want to PUT to example.com/customer/{your customer id}

    It seems that your fundamental issue is that you are dealing with is that you are specifying your action (or verb) in your URL. You don’t need to do that. Instead of doing something like example.com/edit/23, you should use the HTTP PUT method with example.com/23 (or example.com/customers/23).

    Have a look at what is RESTful/REST for a review on creating RESTful resources.

    Have a look at PUT vs POST in REST for the difference between POST and PUT (edit and create).

    For building more complex RESTful URLs, I generally refer to this presentation from the LinkedIn nerds.

    • 0