Condense GET Endpoints #8

Closed
opened 2026-05-22 15:39:31 +00:00 by chris · 1 comment
Owner

There doesn't need to be multiple endpoints getting different data about a single entity, especially when using get by ID. eg

  • [GET] /user/{user_id}
  • [GET] /user/{user_id}/orgs
  • [GET] /user/{user_id}/groups

Can be condensed into a single well-structured [GET] /user/{user_id}

There doesn't need to be multiple endpoints getting different data about a single entity, especially when using get by ID. eg - [GET] /user/{user_id} - [GET] /user/{user_id}/orgs - [GET] /user/{user_id}/groups Can be condensed into a single well-structured `[GET] /user/{user_id}`
Owner

While this is fine for smaller amounts of data, if there's some larger list of things later a ?filter= would be good to avoid using up all the memory in the browser tab for the frontend.

While this is fine for smaller amounts of data, if there's some larger list of things later a ?filter= would be good to avoid using up all the memory in the browser tab for the frontend.
chris closed this issue 2026-05-26 15:24:41 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: sr2/cloud-api#8
No description provided.