Error format
PDFBase uses conventional HTTP status codes and returns errors as JSON with a consistent structure.HTTP status codes
Error types
invalid_request
The request was malformed or missing required fields.
authentication_error
API key is missing, invalid, revoked, or expired.
permission_error
The API key is valid but doesn’t have the required scope, or the request IP isn’t allowed.
not_found
The requested resource doesn’t exist or has expired (files expire after 24h by default).
rate_limit_error
You’ve exceeded your plan’s rate limit. See Rate Limits for details.
rendering_error
The PDF was generated but something went wrong during rendering. The response still includes the PDF, but the warnings field flags issues.
payment_required
Your credit balance is 0. Purchase more credits to continue making API calls that consume credits. Read-only operations (GET endpoints) still work.
idempotency_error
You reused an idempotency key with different parameters than the original request.
internal_error
Something went wrong on our end. These are automatically reported and investigated. Retry with exponential backoff.
Retry strategy
For429 and 5xx errors, retry with exponential backoff:
The
Retry-After header on 429 responses tells you exactly how long to wait. Always respect it.
Billing for errors
You are never charged for failed requests. Only successful PDF generations (statuscompleted or completed_with_warnings) count as credits.