Rate limits

LIGR applies fair-use limits to the REST API. LIGR does not publish a fixed request budget. Unauthenticated requests are limited per IP address. Read the headers on every response, and slow down before they reach zero.

Headers

Every response carries the IETF draft headers.

RateLimit-Limit: 300
RateLimit-Remaining: 287
RateLimit-Reset: 41
RateLimit-Policy: 15;w=1, 300;w=60, 6000;w=3600

Header	Meaning
RateLimit-Limit	The number of requests the current window allows
RateLimit-Remaining	The number of requests left in the current window
RateLimit-Reset	The number of seconds until the current window resets
RateLimit-Policy	Every window in force, as <limit>;w=<seconds>

More than one window can apply at the same time. RateLimit-Policy lists every window in force.

Observe mode

LIGR is phasing enforcement in. While enforcement is off, an over-limit request still succeeds. The response carries x-ligr-rate-limit-observe: 1.

Caution

Treat x-ligr-rate-limit-observe: 1 as a 429 in your client. Back off when you see it. Your requests will fail once enforcement starts.

Enforcement

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

Over the limit

An enforced over-limit request returns 429.

429 Too Many Requests

{ "message": "Api key has made too many requests" }

Wait RateLimit-Reset seconds, then retry.

Stay inside the limits

• 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.