Skip to main content

insufficient-credits

HTTP status: 402 Payment Required Type URI: https://docs.evinor.ai/problems/insufficient-credits

Your account's credit balance can't cover this request. Only billed endpoints can return it — today that is a new event search (POST /v1/events/search without a cursor); see Searching events.

Nothing was charged. The balance is checked before the search runs, so a 402 means the search never executed.

Extension member​

  • as_of — the timestamp of the balance snapshot the check was made against, as an ISO 8601 string.
{
  "type": "https://docs.evinor.ai/problems/insufficient-credits",
  "title": "Insufficient credits",
  "status": 402,
  "detail": "Your credit balance is exhausted.",
  "as_of": "2026-08-06T09:12:33.000Z",
  "request_id": "8f0b2c1e-4a7d-4b93-9c2e-1d5a6f0b3c8e"
}

Common causes​

  • The balance ran out mid-integration — for example a backfill loop issuing one search execution after another.
  • The account's plan or top-up hasn't been applied yet.

How to resolve​

  • Top up the balance from the Evinor app, then retry.
  • The same Idempotency-Key may be reused after a top-up. Because a 402 is a pre-charge refusal, the key's claim is released, so retrying the identical request with the same key executes normally rather than returning a 409. This is the one billed-endpoint failure that does not require a fresh key — see Idempotency.
  • Don't retry on a fixed timer without topping up: the balance won't change on its own, and each attempt still consumes your rate-limit budget.
  • Page through an execution you've already paid for with its next_cursor — continuation pages are not re-charged and can't return a 402.