ConverterHQDevelopers
Documentation

Synchronous and asynchronous conversions

Use one conversion contract for fast and long-running work.

ConverterHQ does not make you choose a different processing system for synchronous and asynchronous work.

Prefer headers

Request preference
Prefer: wait=20
Prefer: respond-async

Bounded waits

If work completes inside the wait window the API returns the completed result. Otherwise it returns 202 Accepted and the persistent Job continues. A client timeout does not imply that the Job was cancelled; query the returned or idempotently recoverable resource before creating duplicate work.

Timeouts and retries

Set your HTTP timeout slightly above the requested wait window and use an idempotency key whenever creation might be replayed. If the connection drops after submission, recover the durable Job rather than assuming the conversion failed. Execution timeout and client wait timeout are separate concepts.

Production pattern

For long-running or high-volume workloads create Jobs asynchronously and use signed webhooks as the durable completion signal. WebSockets/SSE are ideal for UI progress, not durable delivery guarantees.