Rate limits and error codes

The rate limit protects the API against overload and abuse. If you send too many requests in a short time, the server replies with HTTP 429 Too Many Requests and a Retry-After header telling you how many seconds to wait.

Current limits

• The limit is 60 requests per minute per token. It applies equally to all plans (Trial, Standard, Pro and Business).
• LAN agents have a separate limit of 120 requests per minute per agent.
• The limit is counted per token (not per whole user). If you need a higher overall ceiling, create multiple tokens for different use cases (for example one for CI/CD and a separate one for the dashboard).

Error codes

• 401 Unauthorized - missing or invalid token.
• 403 Forbidden - the action is not available on your plan (for example creating a monitor after your plan expired or beyond your plan limit).
• 404 Not Found - the given resource (monitor, incident) does not exist or you have no access to it.
• 429 Too Many Requests - request limit exceeded. Wait the number of seconds given in the Retry-After header.
• 5xx - server-side error. Retry with progressively longer delay (exponential backoff - for example 1, 2, 4, 8 seconds).

Practical recommendations

• Cache responses from read endpoints. Uptime data does not change every second, so you do not need to pull it that often.
• Where possible, use webhooks instead of repeated polling - the server will call you when an event occurs.
• For batch operations, add a short delay between requests so you do not approach the limit.