Skip to main content

Errors, pagination, and safe retries

StatusWhat to check
400Required fields, formats, and workspace context
401Missing, invalid, or inactive token
403Workspace permissions or feature access
404Resource identifier and visibility to your identity
409Conflicting resource state
422Workspace or resource configuration
429Rate limit or quota; honor Retry-After when supplied
5xxTemporary service failure; retain a redacted request record for support

Pagination varies by endpoint. Agent/configuration lists use cursor parameters; call history uses the parameters documented for that route. Follow the endpoint response rather than assuming a universal cursor shape.

Retry safe reads with bounded exponential backoff. Do not automatically repeat call creation, SMS, publication, deletion, or other writes after a timeout: the operation may already have completed. Verify state first unless the endpoint explicitly documents idempotency support.