Errors

Errors use RFC 9457 problem details with Content-Type: application/problem+json:

{
  "type": "about:blank",
  "title": "Request could not be completed",
  "status": 404,
  "code": "not_found",
  "request_id": "..."
}

Use code for program logic; title can change. Include request_id, also returned in the X-Request-Id header, when you contact support.

Status codes

Status	Meaning
`400`	Invalid, duplicate or unsupported parameters. Unknown parameters are rejected.
`401`	Missing, expired or revoked credential.
`403`	The request origin isn’t allowed.
`404`	The resource doesn’t exist, or the caller can’t access it. The two look the same on purpose.
`406`	No acceptable representation. File content only.
`409`	A write conflict or uncertain outcome. See safe writes.
`412`, `416`	A file version or byte range precondition failed.
`422`	The capability isn’t available to application installations.
`429`	Quota reached. Wait for the seconds in `Retry-After`.
`502`	The website’s connector returned an invalid response (`connector_response_invalid`).
`503`	The Gateway, the website’s cluster or a required check is temporarily unavailable.

Code	Meaning
`idempotency_conflict`	The key was used with a different body or different permissions
`operation_in_progress`	The same command is still pending
`operation_conflict`	The website rejected the change
`outcome_unknown`	The result is uncertain; retry with the same key

Code	Status	Meaning
`replay_expired`	`409`	Retained history has expired. Reconcile, then replace the subscription with `"start":"retained"`.
`subscription_revision_changed`	`409`	The subscription was replaced; use the new cursor.
`event_family_paused`	`503`	Delivery is paused. Keep your cursor and retry later.

Status	Retry?
`429`	Yes, after `Retry-After`
`502`, `503`	Yes, with backoff
`409 outcome_unknown`, `409 operation_in_progress`	Yes, with the same idempotency key and body
Other `4xx`	No; fix the request or the credential’s grants first