Skip to content

Request Parameters Too Large

URI: https://docs.ankatech.co/errors/request-parameters-too-large
HTTP Status: 413 Content Too Large

When you see this

A form body sent as application/x-www-form-urlencoded is larger than the size the server parses into request parameters. Every service answers this the same way, on every endpoint, before the request reaches the operation it addresses.

Common Causes

  • A large value, such as a document or a certificate chain, sent as a form field instead of in a JSON or binary body.
  • A form body assembled from an unbounded list of fields.

Response Example

HTTP/1.1 413 Content Too Large
Content-Type: application/problem+json

{
  "type": "https://docs.ankatech.co/errors/request-parameters-too-large",
  "title": "Content Too Large",
  "status": 413,
  "detail": "The request parameters exceed the size the server accepts.",
  "instance": "/api/v3/auth/token",
  "timestamp": 1790973380
}

The detail is fixed. instance is the path you called. The body carries no correlation member; the X-Correlation-Id response header does.

How to Resolve

  1. Send large content in the request body format the operation documents (JSON or a binary stream), not as a form field.
  2. If the operation only accepts a form, reduce the size of the fields you send.

A request body that is too large for the operation itself, rather than for parameter parsing, is answered with Payload Too Large.