Uptimely

rate_limited

HTTP 429 — Rate limit exceeded

rate_limited means the key sent too many requests inside one minute, so the API is asking the client to slow down and retry after a short delay.

What it means

A per-minute limit for this key was exceeded: the general burst (60/min on Free, 300/min on Pro) or, on list, history and export endpoints, the lower list ceiling of 60/min. The `detail` says which. This is about request PACING, not your monthly quota.

Common causes

  • A burst of parallel requests inside one minute window.
  • A loop polling a list endpoint (such as `GET /v1/monitors`) more than once a second. List endpoints have their own 60/min ceiling per key; single-resource reads and writes keep the rest of the burst.
  • A retry loop without backoff.

How to fix it

Honor the `Retry-After` header (seconds until the window rolls), add exponential backoff, and spread bulk work across minutes. The `ratelimit` response headers show the live window state on every response.

Should you retry?

Yes — after `Retry-After` seconds. The official SDK does this automatically.

The response shape

Every /v1 error is an RFC 9457 application/problem+json document: type links to this page, code is the stable value to branch on (never parse title or detail), and request_id identifies the request to support. Validation failures add an errors array of per-field JSON pointers.

API overview · API reference · All error codes: