API errors, limits & retries
Handle failures without turning them into duplicate changes.
HTTP status codes
| Status | Meaning | Next step |
|---|---|---|
| 200 / 201 | Successful read or creation | Parse the documented response format. |
| 204 | Success without a response body | Do not call a JSON parser on the empty body. |
| 401 | Missing, invalid or revoked authentication | Check the bearer header and active credential. |
| 403 | Scope, permission, plan or origin restriction | Read the detail message; do not retry unchanged. |
| 404 | Resource unavailable or not accessible | Check the identifier and account access. |
| 422 | Request validation failed | Inspect the detail entries and fix the named fields. |
| 429 | Rate limit or operation-specific throttle | Wait and use a bounded backoff. |
| 502 | Monitoring backend temporarily unavailable | Retry safe reads later with bounded backoff. |
Read the error body
Application errors normally include a JSON detail value. Validation errors can use an array of entries with field locations and messages. Preserve useful status and detail information in your integration logs, while removing secrets and sensitive request content.
{"detail":"This API key is read-only"}Rate limits
API-key requests are limited to 120 requests per minute per key by the current limiter. Some operations have additional limits, such as monitor creation or imports. The limiter is process-local; do not treat the exact boundary across replicas as a guaranteed allowance.
Not every 429 response includes a Retry-After header. Honor it when present, otherwise apply a bounded exponential backoff with jitter. Avoid continuously polling the same resource when a longer refresh interval will do.
Safe retries
Retry safe reads after a temporary connection failure, 429 or suitable 5xx response, with a maximum attempt count. Do not blindly repeat POST requests after a timeout: the first attempt may already have created the resource. This API does not document a general idempotency-key mechanism.
Null data and response compatibility
A null uptime or response-time value means no suitable data was available; it is not zero. Tolerate additional response fields and avoid relying on object key ordering. Use the OpenAPI document for supported request values rather than guessing field names.
When asking for help
Include the method, path, response status and a redacted error message. Never include API keys, host tokens, log-source tokens or private heartbeat URLs. Open a ticket through Support.