quota_exhausted

What it means

The project's monthly request quota is used up (1,000 requests/month on Free, 100,000 on Pro). `Retry-After` points at the start of the next billing month.

Common causes

• Sustained traffic beyond the plan's monthly allowance.
• A runaway integration polling far more often than needed.

How to fix it

Upgrade the plan, or reduce request volume (poll less often, use webhooks instead of polling — they don't consume quota). `GET /v1/usage` shows live consumption and never consumes or denies.

Should you retry?

Not immediately — automatic retries should stop; the quota resets at the next period.

The response shape

Every /v1 error is an RFC 9457 application/problem+json document: type links to this page, code is the stable value to branch on (never parse title or detail), and request_id identifies the request to support. Validation failures add an errors array of per-field JSON pointers.

API overview · API reference · All error codes:

• missing_credentials — HTTP 401, Missing credentials
• invalid_api_key — HTTP 401, Invalid API key
• invalid_token — HTTP 401, Invalid access token
• unsupported_credential_type — HTTP 403, Credential type not usable on this surface
• insufficient_scope — HTTP 403, Insufficient scope
• feature_not_enabled — HTTP 403, Feature not enabled on this plan
• validation_failed — HTTP 400, Request validation failed
• resource_not_found — HTTP 404, Resource not found
• rate_limited — HTTP 429, Rate limit exceeded
• idempotency_key_reused — HTTP 422, Idempotency-Key reused with a different request
• idempotency_in_progress — HTTP 409, A request with this Idempotency-Key is still in progress
• internal_error — HTTP 500, Internal server error