KEY_SPEND_CAP_REACHED
The publishable key has spent its daily credit cap
The key was created with a daily credit cap and has reached it today. The counter resets each day.
- http status
- 429
- credits
- Nothing is billed for a failed request.
What it means
A daily cap protects your balance from a form that is being abused. Only answered lookups count towards it: undeliverable verdicts, cache hits and test addresses are free and never move the counter.
What to do
Wait for the daily reset, or create a key with a higher cap. The form widget never blocks the visitor's submit when a lookup is refused.
Example response
{
"success": false,
"error": {
"code": "KEY_SPEND_CAP_REACHED",
"message": "This publishable key has reached its daily credit cap. The counter resets each day.",
"request_id": "req_01m1kgdm4xngzmbmff68g94w0c"
}
}Every error carries the request_id also sent in the X-Request-Id header; quote it when writing to support.
Related
- RATE_LIMITED · more requests than the limit allows
- All error codes
- Verdicts and the risk score
- API reference
markdown version: /docs/errors/KEY_SPEND_CAP_REACHED.md