413 · payload_too_large
payload_too_large: the request body is over the per-call allowance
payload_too_large means the body you asked the relay to forward exceeded the per-call allowance. The request was refused before any connection was opened and no trips were charged.
Common causes
- A large JSON body was sent as a single forward.
- A file was base64-encoded into body_base64 — base64 inflates the payload by about a third.
- An automation retried by appending to an existing body rather than replacing it.
How to fix it
- 01Split the work into several smaller forwards instead of one oversized call.
- 02Upload large artefacts to your own storage and send the relay a URL instead of the bytes.
- 03Check the byte count before sending; envelope meta reports bytes_in and bytes_out on successful calls.
What it looks like
payload_too_large
# smaller request, same outcome
{
"url": "https://api.example.com/v1/items",
"method": "POST",
"body": { "ids": [1, 2, 3, 4, 5] },
"timeout_ms": 10000
}Every error code
Questions about this
Related errors
Try it with 5,000 free trips.
No card, no subscription, and the balance never expires.

