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 carried more properties than this endpoint accepts. No Credits were consumed. On the batch endpoint that means more entries in the properties array than the documented limit: split it and send the parts again. On an endpoint that takes a single property, every body member that is not a documented request option counts as a property, so an unrecognised member name is counted as one: check the member names against the API reference and send the request 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 was counted as carrying. On the batch endpoint that is the number of entries in the properties array. On an endpoint that takes a single property it is the number of body members that are not documented request options — so an unrecognised member name is counted as a property and raises this number. |
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.
Contact support at [email protected] and quote the Trace ID.