Spend Cap reached
| HTTP status | 429 |
| Type | https://docs.investorliftdata.com/errors/spend-cap-exceeded |
| Retryable | Yes |
| Retry-After header | No |
What the body says
The response body says:
This Account has reached its Spend Cap, the ceiling on the Credits it may consume in a rolling window, so this Metered Call was not started and no Credits were consumed. The Spend Cap, the Credits already consumed in the window, the Credits this call requires, and the length of the window in seconds are given below. The window rolls continuously rather than resetting on a clock boundary: send the request again once earlier calls have fallen outside it, or contact support to have the Spend Cap raised.
What happened to the Credits
No Credits are consumed by a call that ends here.
Retrying
Retryable. Send the request again.
Body members
Beyond the base members (type, title, detail, status, trace_id), the body
carries:
| Member | Meaning |
|---|---|
cap | The Spend Cap for this Account — the most Credits it may consume in one rolling window. |
consumed | The Credits this Account has already consumed in the window. Every Metered Call counts, including calls that were later refunded. |
required | The number of Credits this Metered Call required. |
window_seconds | The length of the window in seconds. The window rolls continuously rather than resetting on a clock boundary, so Credits become available again as earlier calls fall outside it. |
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.