Credits & billing
How the production credit gate works and what a 402 means.
Production API usage is billed against your organisation's credit balance. Every billable /service call is metered; when the balance is exhausted, the API stops serving billable calls until you top up.
The 402 response
When your organisation is out of credits, any /service call in production returns:
{
"error": "insufficient_credits",
"message": "Organisationen har slut på krediter. Fyll på för att fortsätta."
}with HTTP status 402 Payment Required. Note that unlike other Cerrtify errors, this one carries a message field rather than detail.
Treat a 402 as a hard stop, not a transient error — retrying won't help until the balance is topped up. A sensible client surfaces it to whoever manages your Cerrtify account rather than retrying.
Where balances live
Credit balance, usage history, and top-ups are managed in the Cerrtify dashboard. The API itself has no self-serve billing endpoints.
Sandbox is free
The credit gate only runs in production. Sandbox calls are never billed and never return insufficient_credits, so you can develop and test without watching a balance.