quota_exceeded
HTTP 429 · not billed
{ "error": {
"code": "quota_exceeded",
"message": "…",
"docs_url": "https://pdfcraft.dev/errors#quota_exceeded"
} }When you get it
A free-plan account has used all 100 renders in the current period.
A plan with no overage has used its whole monthly allowance. Free hard-stops; paid plans never do — they accrue overage instead, because hard-stopping a paying customer mid-month is how you lose them.
How to fix it
- Check GET /v1/usage for resets_at.
- Upgrade, or wait for the period to roll.
- Extraction meters per PAGE read, not per document — a 40-page filing is 40 units.
Is it billed?
No. A request is billed only when Chromium actually ran. Only ever on free. If you see it on a paid plan, something is wrong and we want to hear about it.
Reproducing it
curl -i -X POST https://api.pdfcraft.dev/v1/render \
-H "Authorization: Bearer $PDFCRAFT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"html":"<h1>hi</h1>"}'The -i matters: Retry-After and X-Renders-Remaining are headers, and a client that only reads the body throws away the two numbers that tell it what to do next.
Every code
| HTTP | Code | Billed? |
|---|---|---|
| 400 | invalid_request | free |
| 401 | invalid_api_key | free |
| 402 | payment_required | free |
| 404 | not_found | free |
| 408 | render_timeout | free |
| 422 | render_failed | billed |
| 429 | rate_limited | free |
| 429 | quota_exceeded | free |
| 429 | demo_busy | free |
| 415 | unsupported_file | free |
| 422 | extraction_failed | free |
| 500 | internal_error | free |