Skip to content

Payload too large

HTTP 413payload_too_large

When the API answers 413 payload_too_large, and how to fix it.

Version v1.1, updated

The type field of every payload_too_large response links to this page.

On this page

The body is larger than 1 MB. Nothing was written.

At a glance

  • Status: 413 Content Too Large

  • Code: payload_too_large

  • Retry: No. Fix the cause first: the same request gets the same answer.

Causes and fixes

Likely cause

How to fix it

A batch carries too much data, even under 100 items.

Send fewer items per batch, so each body stays under 1 MB.

A text field carries a very large value, such as a long description.

Shorten it to what BIRP needs.

Example

413 payload_too_largeJSON
{
  "code": "payload_too_large",
  "detail": "The request body is larger than the limit.",
  "instance": "/v1/categories",
  "request_id": "a1b2c3d4-0000-4000-8000-0000000000ee",
  "status": 413,
  "title": "Payload too large",
  "type": "https://birp.io/developers/errors/payload_too_large"
}

Related

  • batches
  • requests
  • errors-overview