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.
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.
What else changed
- Above 2 MB →
413 REQUEST_BODY_TOO_LARGE, with the limit and the declared size inerror.details - Above 8 MB →
413 PAYLOAD_TOO_LARGE, rejected at the edge - File uploads keep their own lower per-endpoint limit, reported as
FILE_TOO_LARGE 411 LENGTH_REQUIREDno longer exists — a body sent with chunked encoding is accepted
Where to go next
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.
A lost update now answers 409 instead of overwriting or failing opaquely
When two updates to the same resource overlap, the one that arrives second answers `409 CONCURRENT_MODIFICATION` instead of silently discarding the other's change or surfacing an internal error. Re-read the resource and retry.