API errors
PDF rendering temporarily unavailable
The hybrid-PDF rendering step (ZUGFeRD/Factur-X) could not complete. Nothing was billed for this request.
- Error type
https://normbill.com/docs/errors/pdf-unavailable- HTTP status
- 503
Common causes
- The PDF sidecar timed out or is briefly restarting; after repeated failures a short circuit breaker fails fast.
- The deployment has hybrid-PDF output disabled (PDF_URL not configured).
How to fix it
- Retry after a few seconds — the circuit closes automatically.
- If you only need the structured payload, generate with format xrechnung-3.0 or peppol-bis-3.0 — the XML is returned without the PDF step.
- If the condition persists, contact support@normbill.com.
The error response format
Every non-2xx response from the API is an RFC 9457 problem-details body (application/problem+json) with at least type, title, status and detail. The type URL links back to this reference.
All error slugs: invalid-request, bad-request, payload-too-large, unauthorized, validation-failed, unparseable-document, plan-limit, quota-exceeded, rate-limited, overage-cap-reached, validate-fair-use, idempotency-key-invalid, idempotency-key-reuse, idempotency-conflict, pdf-unavailable, validator-unavailable, not-ready. Still stuck? Email support@normbill.com or start at the docs overview.