Errors, retries, and request IDs

Error format

Every API error contains error.code, error.message, and error.request_id. The SDKs convert unsuccessful responses into their language-specific errors; the CLI prints the code, HTTP status, and request ID when available.

Status	Typical meaning	Action
400	Invalid input or unsupported mutation body	Correct the request; do not blindly retry.
401	Missing, invalid, expired, or revoked credential	Verify the credential source and create or reconnect if needed.
403	Key or OAuth token lacks the required scope	Grant the least additional scope needed.
404	Resource does not exist, is not owned by the account, or is not linked to the product system	Verify the ID and account.
409	Idempotency conflict or conflicting resource state	Reuse the original key only for the same request; inspect the current resource state.
5xx	Unexpected server or upstream failure	Retry only safe reads or the same write with the same idempotency key.

Retry a mutation

Keep the original idempotency key, wait using bounded backoff, and repeat the exact request. Do not generate a new key until you intend a new logical action. For queued operations, follow with a read request or check the customer console. Include request_id, approximate timestamp, endpoint, and sanitized response when reporting a problem. Never include an API key, password, panel link, or infrastructure credential.

​Error format

​Retry a mutation

Error format

Retry a mutation