Timeline for How to structure URL when retrieving a REST resource by an attribute that isn't the ID?
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 26, 2021 at 14:19 | vote | accept | Cork | ||
| Oct 26, 2021 at 14:18 | comment | added | Cork | Thanks! FYI, the "car" example is used to hide proprietary stuff I'm doing. My API abstracts existing data across sources that will eventually have internal IDs, but often does not. We are in the process of consolidating this data. The result is that we want to build our API so that the path to the resource IS structured with an internal identifier that will someday exist, but still allow us to retrieve a resource in other ways in the meantime. I'll either absorb a child into the parent, or otherwise use the HATEOAS approach of linking to related resources so all resources have IDs. | |
| Oct 26, 2021 at 5:26 | history | answered | Hans-Martin Mosner | CC BY-SA 4.0 |