Error: body_too_large
The request body exceeded the server's size limit.
What it means
The API enforces a maximum request body size. Bodies over the limit are rejected before parsing with 413.
Common causes
Accidentally sending a huge payload (e.g. a full document instead of a transaction).
A client retrying a corrupted buffer.
How to fix
Send only the transaction fields the API expects: amount, currency, merchant, category, timestamp.
Check for streaming/client-side buffering bugs that inflate the body.
At a glance
| Field | Value |
|---|---|
| HTTP status | 413 |
| Error code | body_too_large |
| Response shape | {"error": "body_too_large"} |
FAQ
What's the size limit?
The server enforces a fixed cap on request bodies; keep payloads small and structured.
Can body_too_large happen on evaluate?
Only if the client sends an oversized body — a transaction object is tiny, so this usually indicates a client bug.
Related
Stop the next $12,400 night.
One API call (or MCP tool) in front of every agent transaction — APPROVED, BLOCKED, or FLAGGED, deterministic, ~5 ms, fully logged.
See plans — from $99/mo Try a live check