|
|
|
|
|
by iamphilrae
3294 days ago
|
|
I just had this exact 'problem' with an API I'm building. I just ended up creating both routes which accessed the same internal function to return the same results - no duplication of code necessary. Personally I think this is a good resolve as it answers both use cases depending on the accesssors context. |
|
/accounts/{id}/users
And
/users/account/{id}
Both return the users attached to a particular account.