Skip to content

Rate limits

LIGR applies fair-use limits to the REST API. LIGR does not publish a fixed request budget. LIGR counts each request with a valid API key against the organization that owns the key. All keys of one organization share one budget, so a new key does not add budget. A request without a valid API key counts against its client IP address. Read the headers on every response, and slow down before they reach zero.

Every response carries the IETF draft headers.

RateLimit-Limit: 24000
RateLimit-Remaining: 23987
RateLimit-Reset: 2041
RateLimit-Policy: 24000;w=3600
HeaderMeaning
RateLimit-LimitThe number of requests the current window allows
RateLimit-RemainingThe number of requests left in the current window
RateLimit-ResetThe number of seconds until the current window resets
RateLimit-PolicyThe window that the other headers describe, as <limit>;w=<seconds>

The headers describe the budget of the request: the organization of the API key, or the client IP address. Three windows apply at the same time: one second, one minute and one hour. On a successful response, the headers describe the one-hour window. On a 429, they describe the window that refused the request. Keep bursts short, because the headers do not show the shorter windows.

Production does not enforce the limits today. While enforcement is off, an over-limit request still succeeds. The response carries x-ligr-rate-limit-observe: 1.

Enforcement starts on a date to be announced in the changelog. Until then, treat x-ligr-rate-limit-observe: 1 as a 429.

An enforced over-limit request returns 429. The body names the budget that refused the request.

RequestBudget429 body
With a valid API keyThe organization of the key{ "message": "Organization has made too many requests" }
Without a valid API keyThe client IP address{ "message": "Client IP address has made too many requests" }

Wait RateLimit-Reset seconds, then retry.

  • Use webhooks instead of polling.
  • Batch reads with include so one request replaces four.
  • Cache GET responses on your side.
  • Contact support if your integration needs a higher limit.