rate_limited

HTTP 429 · not billed

{ "error": {
    "code": "rate_limited",
    "message": "…",
    "docs_url": "https://pdfcraft.dev/errors#rate_limited"
} }

When you get it

More requests per second than the plan allows.

More requests per second than the plan allows, measured over a sliding window rather than a fixed one — so a burst cannot straddle a boundary and get twice the allowance.

How to fix it

• Honour Retry-After and back off. It is the number of seconds until the window has room.
• Paid plans allow 20 requests a second; Business allows 150.
• For bulk work use /v1/render/async and let the queue pace it.

Is it billed?

No. A request is billed only when Chromium actually ran. Per key, so splitting work across two keys on one account does not help — and per-second, so it is a burst problem rather than a volume problem.

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