payload_too_large

HTTP status

413

Title

Request body too large

Code

payload_too_large

What it means

The request body is larger than the operation accepts.

It is also the catch-all of status 413: an error of that status that has no more specific code answers with this one.

What to do

Send less. Files go to an upload URL, never in an API body.

Example

Errors are RFC 9457 problem details, sent as application/problem+json. See Errors for every field.

{
  "type": "https://docs.furniops.com/errors/payload_too_large",
  "title": "Request body too large",
  "status": 413,
  "code": "payload_too_large",
  "detail": "An explanation of this occurrence.",
  "request_id": "req_…",
  "doc_url": "https://docs.furniops.com/errors/payload_too_large"
}

Operations that answer it

• PATCH /v1/agents/{agent}
• POST /v1/agreements/{kind}/acceptances
• POST /v1/assistant/conversations
• POST /v1/assistant/conversations/{conversation}/turns
• PATCH /v1/assistant/me
• POST /v1/assistant/memories
• PATCH /v1/assistant/memories/{memory}
• PATCH /v1/assistant/settings
• POST /v1/billing/credits/purchases
• POST /v1/billing/credits/purchases/preview
• PATCH /v1/billing/credits/settings
• PATCH /v1/billing/details
• POST /v1/billing/preview
• POST /v1/billing/subscription
• PATCH /v1/brand
• POST /v1/brand/claims
• POST /v1/brand/invitations/preview
• POST /v1/catalogue/visibility
• POST /v1/catalogue/withdraw
• POST /v1/demand
• POST /v1/exports
• POST /v1/mappings/{id}/confirm
• PATCH /v1/matching/judge-settings
• POST /v1/proposals/{id}/reject
• POST /v1/source-probes
• POST /v1/sources
• PATCH /v1/sources/{id}
• POST /v1/sources/{id}/categories
• PUT /v1/sources/{id}/credentials
• POST /v1/sources/{id}/records
• POST /v1/sources/{id}/runs
• POST /v1/sources/{id}/uploads
• POST /v1/test/events
• POST /v1/webhook-endpoints
• PATCH /v1/webhook-endpoints/{id}
• POST /v1/webhook-endpoints/{id}/recover
• POST /v1/webhook-endpoints/{id}/rotate-secret