Errors

API errors normally use this JSON envelope:

{ "code": "error_code", "message": "Readable explanation", "requestId": "request-id" }

Some errors also include details, for example field validation failures. Use the HTTP status and code to decide how to respond; keep requestId, the endpoint and request time when reporting a problem. Do not include your API key in a support report.

Status	Meaning	Next step
400 / 422	Invalid input or an unsupported operation for this record	Check the response code, details and request schema before retrying.
401	Missing or invalid API key	Check the Authorization header and key.
403	Missing scope or an operation not allowed for the account	Check the key's scopes and resource restrictions.
404	The resource was not found or is not available to this account	Check the ID and account context.
409	A conflicting record or state	Read the existing resource before retrying.
429	Request rate or monthly allowance exceeded	Follow Retry-After and the rate-limit guidance below.
500 / 503	Server error or temporary unavailability	Preserve request details; follow Retry-After when provided.

Edge firewall rejections occur before the request reaches the API. An IP rate-limit rejection returns 429 rate_limit_exceeded without requestId. A blocked attack pattern or an IP reputation rule can return 403 with a non-JSON body. Report the endpoint and request time for these cases.