Errors and pagination
Handle bounded results and uncertain outcomes without repeating side effects.
API 2.7.0 · Published service contract ↗
Pagination
Use limit and cursor only on endpoints that document them. A cursor is opaque. Continue with next_cursor until it is null; preserve the same filters. Each operation documents its limit.
Error responses
| Status | Meaning | Next step |
|---|---|---|
| 400 | Invalid input | Correct the documented schema. |
| 401 | Missing, expired or wrong credential | Check the required credential type. |
| 403 | Scope or current access denied | Check membership, Agent access and granted scopes. |
| 409 | Conflict or current-state restriction | Read the latest state before acting. |
| 429 | Rate limit | Honor retry_after_seconds or Retry-After. |
| 503 | Service unavailable or outcome uncertain | Inspect existing state and receipts before retrying a mutation. |
Request identity
Retain request identifiers for writes that accept them. A timeout is not proof an operation did not run. Never invent a new request identity to bypass an uncertain outcome.
Versions
This reference uses the published Workspace API 2.7.0 contract. The URL prefix remains /v1. Endpoint-specific response examples describe the wire format, not your current workspace state.