Theme
Batch too large
413 · BATCH_TOO_LARGE
More entries in one call than the endpoint allows. Nothing was written.
json
{
"type": "about:blank",
"title": "Batch too large",
"status": 413,
"code": "BATCH_TOO_LARGE",
"detail": "At most 50 links can be created per request; received 120. Split the batch and retry."
}| Endpoint | Maximum per request |
|---|---|
POST /campaigns/{campaign_id}/links | 50 links |
POST /conversation-metadata | 300 rows |
Separately, every request body is limited to 64 KB. A body over that never reaches the API, so it gets an HTML 403 instead of this error (see Handling errors). For conversation metadata that limit usually comes first: split by size.
Why 50 links
Each request writes every link plus a campaign counter in one database transaction, and that transaction has a hard ceiling. Fifty is what fits with room for the counter.
Either way, an oversized batch is refused rather than silently truncated, so a batch never half-lands without telling you.
What to do
Split the batch into chunks no larger than the maximum and send them in sequence. Each chunk spends one write against your rate limit, not one per entry, so batching is what keeps you inside the budget.
