unsupported_file

HTTP 415 · not billed

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

When you get it

The file is not a PDF, is password-protected, or is corrupt beyond parsing.

The bytes are not a PDF, are encrypted, or are damaged past parsing. Encrypted and corrupt are distinguished in the message, because the fixes are nothing alike.

How to fix it

• Decrypt the file before sending. There is deliberately no password option in the contract — accepting one would mean holding a customer document password in a request log.
• Check the upload is not truncated: base64 that decodes short arrives here rather than as a network error.

Is it billed?

No. A request is billed only when Chromium actually ran. Not billed. Nothing was parsed.

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