Reference
Limits and error reference
Understand the categories of limits and failures an integration must handle.
Reviewed 2026-08-05 · PDFDesignAPI Engineering
Limit categories
The service enforces team-scoped concurrency, request rate, monthly usage, and synchronous payload limits. Exact commercial limits can vary by plan and current product configuration; use current account/pricing information rather than hard-coding marketing values.
Async results and synchronous idempotency results expire after 24 hours.
Error categories
Handle authentication and authorization, unknown template/version/environment, conflicting selectors, invalid idempotency key, changed or concurrent idempotent request, schema validation, oversized payload, rate/usage limit, render failure, and expired result.
Use the HTTP status and structured response rather than parsing error text.
Support context
When escalation is required, provide endpoint, timestamp, safe correlation ID, template UUID, selected version/environment, and status category. Redact customer data and credentials.