Home/ Questions/Q 6716561
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T08:44:54+00:00

In an ideal RESTful API that supports multiple accounts, should each resource have it’s

  • 0

In an ideal RESTful API that supports multiple accounts, should each resource have it’s unique identifier across the entire system, or it is OK if that identifier is unique for the specific account that it belongs to.

Are there any pros and cons for each scenario?

To give an example.

Would this be fine from the REST principles?

http://api.example.com/account/1/users/1
...
http://api.example.com/account/50/users/1

or would this approach be recommended?

http://api.example.com/account/1/users/{UNIQUE_IDENTIFIER}
...
http://api.example.com/account/50/users/{ANOTHER_UNIQUE_IDENTIFIER}
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You reveal valid user numbers by always having the first user as 1. Someone then knows that any account will also have a user 1. I’m not saying that you should hide user IDs just through obscurity but why make it easy for someone to find the user IDs in another account?

    • 0