Error reference / bulk-too-many-rows
Too many rows in one bulk send
A bulk send takes at most 5,000 rows.
| Problem type | /problems/bulk-too-many-rows |
|---|---|
| HTTP status | 422 |
| Emitted by | REST API (/v1) |
| Title values | Too many rows |
| Extra members | max_rowsrows |
| Trigger | REST API (/v1): a bulk send above the 5,000-row ceiling (D56) |
What happened
POST /v1/bulk-sends received more than 5,000 rows. The response is HTTP 422 with max_rows and the count received.
What it means
Nothing was stored or sent. The ceiling is per request, not per day; your monthly allowance and the daily review threshold apply separately at dispatch.
What to do next
Split the file into batches of 5,000 rows or fewer and create one bulk send per batch.
Problem body
Every error is an RFC 9457 problem document with media type
application/problem+json. The type member is the
stable identifier to switch on; docs_url is this page.
{
"type": "/problems/bulk-too-many-rows",
"title": "Too many rows",
"status": 422,
"instance": "/v1/...",
"docs_url": "https://docs.signenvoy.com/errors/bulk-too-many-rows",
"max_rows": "...",
"rows": "..."
}