Handling errors
Machine-readable errors following RFC 9457.
Errors use the application/problem+json content type. Branch on code and the HTTP status. detail explains the error; errors may contain field errors with dot-separated paths. request_id links your request to the server log.
{
"type": "https://developers.adlass.io/errors/insufficient_scope",
"title": "Insufficient scope",
"status": 403,
"code": "insufficient_scope",
"required_scope": "spaces:write",
"request_id": "req_…"
}| Status | Action |
|---|---|
| 400 | Check parameters and the Idempotency-Key |
| 401 | Check the key, environment, expiration, and revocation |
| 403 | Check scopes and user permissions |
| 404 | The resource or route is unavailable |
| 409 | Resolve the business conflict |
| 422 | Do not reuse an Idempotency-Key for a different intent |
| 429 | Wait for Retry-After |
| 5xx | Retry a limited number of times with the same idempotency key |
The type link opens the reference for the specific error code. Provider internals are not exposed. Include request_id in support requests, never the API key.