> ## Documentation Index
> Fetch the complete documentation index at: https://apidocs.scripe.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Payload too large

# `payload_too_large`

| HTTP | When                                                 |
| ---- | ---------------------------------------------------- |
| 413  | The request body exceeded the per-endpoint size cap. |

Each write endpoint enforces a hard cap on the size of the JSON body so
a single client can't pin a server with a multi-megabyte payload. The
caps are:

| Endpoint                  | Cap                                       |
| ------------------------- | ----------------------------------------- |
| `POST /v1/notes`          | 100 KB on `content`                       |
| `POST /v1/posts`          | 100 KB on `content`, 500 chars on `title` |
| `POST /v1/sources` (text) | 1 MB on `text`                            |

When you send an `Idempotency-Key` we additionally cap the **total**
request body at 256 KB by default (sources push this to its own cap)
because we have to buffer the body in memory to hash it for replay.

## Recovery

1. Trim or chunk the offending field.
2. For long-form transcripts that genuinely don't fit, split them into
   multiple sources and link them client-side.
3. The 1 MB cap on `text` sources is a hard product decision; if your
   workflow needs more, file a feature request — file-ingest sources
   (with S3 multipart uploads) are the long-term answer.

The error envelope is the same uniform shape; the `message` field will
hint which field tripped the cap.