Quotas and rate limits
One rule covers quotas: every counted capture session is one attempt, whatever happens to it. The attempt is spent when the session is created.
GET
/v1/usage- Live sessions count, including rejected, retried and abandoned ones.
- On the Developer plan, sandbox sessions count too, because the sandbox is all that plan has. On paid plans they don't.
- When attempts run out, new sessions return 429 quota_exceeded until the next period.
- Warka never charges overage automatically.
- You get a usage.threshold event and an email at 80% and at 100%.
Rate limits
Limits apply per organization and environment, so all your keys and calls share them. Extra keys don't add capacity. Sandbox is capped at 5 requests per second, or lower if your plan is. One verification uses two limited calls, creating the session and verify. Frame uploads use the capture token and aren't counted. Every response to an API-key request carries the headers below.
| Header | Meaning |
|---|---|
| X-RateLimit-Limit | Requests allowed in this window |
| X-RateLimit-Remaining | Requests left |
| X-RateLimit-Reset | Unix time the window ends |
| Retry-After | Seconds to wait, on 429 and 503 |
A 503 overloaded response means the service is at capacity. The session stays usable, so wait for Retry-After and call verify again.