Errors
The API uses conventional HTTP status codes. Error bodies are JSON with a message you can log.
| Code | Meaning | Fix |
|---|---|---|
| 400 Bad Request | Malformed request or invalid field values. | Check the request body against the API reference; fix the offending field. |
| 401 Unauthorized | Missing or invalid Bearer key. | Send Authorization: Bearer amk_… with a valid, non-expired key. |
| 403 Forbidden | The key lacks permission for this resource. | Use a key whose organization/role grants the action; check your plan. |
| 404 Not Found | The resource doesn’t exist or isn’t in your org. | Verify the id and that it belongs to the key’s organization. |
| 422 Unprocessable | Validation failed (e.g. invalid status value). | Use an allowed enum value; see the field’s schema in the reference. |
| 429 Too Many Requests | Rate limit exceeded. | Back off and retry with exponential delay; batch where possible. |
| 500 Server Error | An unexpected error on our side. | Retry; if it persists, contact support with the request id. |
400 Bad Request
Malformed request or invalid field values.
Check the request body against the API reference; fix the offending field.
401 Unauthorized
Missing or invalid Bearer key.
Send Authorization: Bearer amk_… with a valid, non-expired key.
403 Forbidden
The key lacks permission for this resource.
Use a key whose organization/role grants the action; check your plan.
404 Not Found
The resource doesn’t exist or isn’t in your org.
Verify the id and that it belongs to the key’s organization.
422 Unprocessable
Validation failed (e.g. invalid status value).
Use an allowed enum value; see the field’s schema in the reference.
429 Too Many Requests
Rate limit exceeded.
Back off and retry with exponential delay; batch where possible.
500 Server Error
An unexpected error on our side.
Retry; if it persists, contact support with the request id.