Pagination And Filtering
Pagination and filtering keep API responses usable when a workspace has many artifacts, events, links, members, or operations.
How To Use This Page
- Use pagination controls instead of assuming one request returns everything.
- Apply filters that match the user task, such as artifact kind or search query.
- Preserve cursors or pagination metadata when building clients.
Developer Checklist
- Confirm the workspace, artifact, bot, server, or operation reference comes from a prior response or visible product route.
- Check authentication and role requirements before sending a request.
- Use response data to drive the next call instead of reconstructing identifiers from display text.
- Preserve visible error details when debugging.
Media To Add
- Table: endpoint type, useful filters, and pagination behavior. It helps developers design efficient clients. Source: public route groups.