# REQUEST_BODY_TOO_LARGE

The request body exceeds the maximum allowed size of ‹max size›.

<Callout type="info">
**Category:** [General](/errors/category/shared)
</Callout>

| | |
|---|---|
| HTTP status | `413` Content Too Large |
| Retry | After fixing the cause |

## When it happens

The request body is larger than the API accepts. It is rejected before being read. `error.details` carries `max_size_formatted`, `max_size_bytes` and `request_size_bytes`.

## How to fix it

Send a smaller body: split a large batch into several calls. For files, use the upload operations, which have their own limits.

## Retry

Not as is: the same request fails the same way. Fix the cause described above, then send the request again, under a new `Idempotency-Key` if the body changed.

## Example response

When this error occurs, the API answers `413` Content Too Large with a JSON body of this shape:

```json
{
  "type": "https://docs.beel.es/errors/REQUEST_BODY_TOO_LARGE",
  "title": "REQUEST_BODY_TOO_LARGE",
  "detail": "The request body exceeds the maximum allowed size of ‹max size›.",
  "instance": "/v1/<resource>",
  "errors": [],
  "success": false,
  "error": {
    "code": "REQUEST_BODY_TOO_LARGE",
    "message": "The request body exceeds the maximum allowed size of ‹max size›.",
    "details": {}
  },
  "meta": {
    "timestamp": "2026-05-21T10:00:00Z",
    "request_id": "4bf92f3577b34da6a3ce929d0e0e4736"
  }
}
```

The `type` URI is stable and always resolves to this page.

## Message

<Tabs items={["English", "Spanish", "Catalan"]}>
  <Tab value="English">{"The request body exceeds the maximum allowed size of ‹max size›."}</Tab>
  <Tab value="Spanish">{"El cuerpo de la petición excede el tamaño máximo permitido de ‹max size›."}</Tab>
  <Tab value="Catalan">{"El cos de la petició supera la mida màxima permesa de ‹max size›."}</Tab>
</Tabs>

Send the request with `Accept-Language: <es|en|ca>` to receive the message in your preferred language.

Placeholders are filled in at runtime:

- `‹max size›` — the maximum body size, formatted for display.

## Other errors in this category

<div className="grid grid-cols-2 gap-3 not-prose">
  <Card title="AUTOMATIC_EMAIL_CONFIG_INVALID" description="For automatic sending, you must provide an email configuration or a client with email" href="/errors/AUTOMATIC_EMAIL_CONFIG_INVALID" />
  <Card title="BAD_REQUEST" description="The provided data is not valid." href="/errors/BAD_REQUEST" />
  <Card title="BUSINESS_RULE_VIOLATION" description="The operation breaks a business rule." href="/errors/BUSINESS_RULE_VIOLATION" />
  <Card title="CITY_EMPTY" description="City cannot be empty" href="/errors/CITY_EMPTY" />
  <Card title="CITY_MAX_LENGTH" description="City cannot exceed ‹value› characters" href="/errors/CITY_MAX_LENGTH" />
</div>

## Keep exploring

<div className="grid grid-cols-2 gap-3 not-prose">
  <Card title="All General errors" description="Every code in this category in one table." href="/errors/category/shared" />
  <Card title="Error reference home" description="Browse every category or jump to the handling guide." href="/errors" />
</div>

---

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