STANDARD STARTER CONTRACT / payload-too-large

Payload too large

The request content is larger than the server is willing or able to process.

HTTP 413

Canonical type URI

https://errors.ctrlbox.dev/problems/payload-too-large

This stable URI identifies the problem type, not a particular occurrence.

What to do next

Reduce the request size or use a supported upload mechanism.

HTTP response contract

Set the actual HTTP status to 413 and Content-Type: application/problem+json. The JSON status below must agree with the actual response status.

Retry-After

If this condition is temporary, the server SHOULD send Retry-After to indicate when a retry is appropriate. A smaller request may still be needed.

RFC-defined members

type: The canonical URI above; clients use it as the primary problem identifier.
title: Payload too large — a stable human-readable summary (localization is permitted).
status: 413 — advisory in the body; it does not set the HTTP status.
detail: A safe explanation specific to this occurrence. Clients should not parse it for machine decisions.
instance: An optional URI reference identifying a specific occurrence. It need not resolve; avoid sensitive identifiers.

These five members are defined by RFC 9457. This template includes type, title, status, and detail in its samples; RFC 9457 does not require all five.

Custom extension fields

This definition declares no custom extensions.

Extensions belong to this type’s contract. Consumers must ignore extensions they do not recognize.

Example response body

Illustrative occurrence data. Construct the response manually in your application or automation.

Example

{
  "type": "https://errors.ctrlbox.dev/problems/payload-too-large",
  "title": "Payload too large",
  "status": 413,
  "detail": "The request content is larger than the server is willing or able to process."
}

Keep established public type URIs stable. The names here are template conventions, not an RFC catalogue. Read the response guide for manual setup and standards references.