Timeline for What is the limit on REST API resource levels
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 29, 2015 at 11:51 | comment | added | Timmetje | What if a freelancer works at two companies? GET /api/companies/1/employees/123/tasks should only return tasks from a person at that company. GET /api/employees/123/tasks gets all tasks from an employee. so these resource urls can both exists but differ from deliverable. | |
| Nov 20, 2013 at 17:32 | vote | accept | supercell | ||
| Nov 18, 2013 at 20:23 | history | edited | Matthew Flynn | CC BY-SA 3.0 | added 1 characters in body |
| Nov 18, 2013 at 19:33 | answer | added | thorsten müller | timeline score: 6 | |
| Nov 18, 2013 at 18:00 | comment | added | Robert Harvey | As far as I know, there's no limit to the number of sublevels; it's all about how you program the routing engine you're using to manage the URLs. So design an API that makes sense to you. The examples you've provided so far seem sensible. | |
| Nov 18, 2013 at 17:45 | history | edited | supercell | CC BY-SA 3.0 | added 155 characters in body |
| Nov 18, 2013 at 17:35 | history | asked | supercell | CC BY-SA 3.0 |