Rate limits

Each API key has a request quota per time window. Successful responses tell you where you stand, in two headers:

RateLimit-Policy: "default";q=100;w=60
RateLimit: "default";r=99;t=60

• RateLimit-Policy: the quota (q) per window of w seconds. Read your actual numbers from this header; the values above are only an example.
• RateLimit: requests left (r) in the current window and seconds until it resets (t).

Over the limit, the API answers 429 with a Retry-After header (in seconds) and a problem+json body of type https://linkspect.com/problems/rate-limited:

HTTP/1.1 429 Too Many Requests
Retry-After: 30
Content-Type: application/problem+json

{
  "type": "https://linkspect.com/problems/rate-limited",
  "title": "Too many requests",
  "status": 429,
  "detail": "The rate limit of this API key is exceeded. Retry after 30 seconds.",
  "instance": "/v1/checks"
}

Wait that long, then retry. Prefer: wait on create usually saves requests compared with polling right away.