HTTP status codes
| Status | Meaning | Recommended action |
|---|---|---|
| 400 | Invalid request or validation failure | Check field names, types, required values and pagination. |
| 401 | Missing, invalid, expired or revoked key | Verify the credential or rotate it through private settings. |
| 403 | Operation or source IP is not permitted | Review key permissions and configured access restrictions. |
| 404 | The requested record or endpoint was not found | Check identifiers, paths and organization ownership. |
| 429 | A request budget has been exceeded | Wait and retry with bounded exponential backoff. |
| 500 | Unexpected server error | Retry safe reads with backoff; contact support if it persists. |
Validation errors
{
"data": null,
"meta": null,
"errors": [
{
"field": "name",
"message": "Required",
"code": "invalid_type"
}
]
}
Rate limiting
API keys have configured request budgets; additional service protections can also limit traffic. Do not hardcode an unlimited request rate. Respect rate-limit or retry headers when present and use bounded exponential backoff with jitter on 429 responses.
Retry writes carefully
Do not assume every write supports idempotency keys. If a request times out, check the resulting record before retrying a create or another non-idempotent operation.