Batch too large
| HTTP status | 413 |
| Type | https://docs.investorliftdata.com/errors/payload-too-large |
| Retryable | No |
| Retry-After header | No |
What the body says
The response body says:
This request submitted more properties than the documented batch limit allows. No Credits were consumed. Split the request into smaller batches and send them again.
What happened to the Credits
No Credits are consumed by a call that ends here.
Retrying
Not retryable. Sending the same request again returns the same error. Change the request as the detail directs before sending it again.
Body members
Beyond the base members (type, title, detail, status, trace_id), the body
carries:
| Member | Meaning |
|---|---|
limit | The documented maximum number of properties a single request may submit. |
submitted | The number of properties this request submitted. |
Retry-After
No. This response carries no Retry-After header.
Every error response is an RFC 9457 Problem Detail sent as application/problem+json,
and every response carries a trace-id header, repeated in the body as trace_id.
The Trace ID is the only handle support needs to find your call.
Last modified on