# Request bodies limited to 2 MB

Bodies above 2 MB answer `413 REQUEST_BODY_TOO_LARGE`. `411 LENGTH_REQUIRED` is gone — chunked encoding is accepted.

Aug 22, 2026 · Breaking

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 in `error.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_REQUIRED` no longer exists — a body sent with chunked encoding is accepted

## Where to go next

- [Handling errors](/guides/handling-errors)
- [Error codes](/errors)

---

Full OpenAPI spec: https://docs.beel.es/api/openapi