The global rate limit drops to 1000 requests per minute
The ceiling that applies to every request, whatever the endpoint, goes from 2000 to 1000 requests per 60 seconds. The per-endpoint tiers are unchanged. An integration that bursts above the new figure will start seeing 429 where it did not before.
The ceiling that applies to every request, whatever the endpoint, goes from 2000 to 1000 requests per 60 seconds. The per-endpoint tiers are unchanged. An integration that bursts above the new figure will start seeing 429 where it did not before.
What else changed
- Global: 1000 req / 60 s (was 2000)
- Standard and Strict tiers unchanged — 300 and 5 req / 60 s
- Exceeding it still returns
429withRATE_LIMIT_EXCEEDEDandRetry-After
Where to go next
Resources under the NIF
An account can now hold several NIFs, each named in the path. The old flat routes are deprecated with a Sunset date and a successor — here's what moved where, when the old routes retire, and how to tell whether it affects you.
Request bodies now have a 2 MB limit, with its own error code
A body above 2 MB is now rejected by the API with `413` and the new error code `REQUEST_BODY_TOO_LARGE`, whose `error.details` carries the applicable maximum and the size the request declared. The 8 MB ceiling still exists but is enforced at the network edge, before the request reaches the API, and keeps answering `PAYLOAD_TOO_LARGE`. Chunked transfer encoding is no longer rejected: `411 LENGTH_REQUIRED` is gone. The largest body the API expects is a bulk import at its declared `maxItems`, comfortably under 2 MB. If you are approaching it, split the batch.