Errors, retries, and limits
Build integrations that retry safely, respect product limits, and remain predictable under load.
Error envelope
{
"error": {
"code": "invalid_request",
"message": "A readable explanation",
"requestId": "req_..."
}
}400invalid_requestMalformed input or a validation failure.401unauthorizedMissing, expired, revoked, or invalid credentials.403forbiddenThe scope, role, or operator boundary denied access.404not_foundThe resource is missing or inaccessible.409idempotency_conflictThe retry key was reused with different input.413body_too_largeThe request exceeded the body limit.429rate_limit_exceededThe workspace machine-call budget is exhausted.500internal_errorA transient internal failure occurred.Idempotency
Use a unique Idempotency-Key for writes. A completed result is replayed for 24 hours. The same key with different input is rejected.
Retry 429 and transient 5xx responses with exponential backoff and jitter. Retry writes only with the same idempotency key and identical body.
Machine rate limits
Default workspace buckets allow 120 reads and 30 writes per minute. Deployments can lower or raise those server-owned limits. Every response reports the limit, remaining calls, and reset time; 429 responses include Retry-After.
Product and provider limits
Agent access never bypasses keyword, mention, project, member, alert, provider, webhook, or billing entitlements. Multiple credentials share the same workspace resources.