Skip to main content

GET /jobs/

When the system is at maximum capacity, any conversion endpoint (/convert, /convert/raw, /convert/from-url, /convert/stream, /convert/stream-from-url, /convert/accelerated) may return 202 Accepted instead of 200. This means that your request was accepted and queued for processing as soon as there is capacity. The 202 response includes a job_id and a URL to query the status:

Check status

Possible answers

The job is queued, waiting for a free backend.
  1. Receive 202 → wait retry_after_seconds (5s by default).
  2. Call GET /jobs/{job_id}.
  3. If status is queued or processing, wait 5s and repeat.
  4. If status is completed, use body as the result.
  5. If status is failed, retry the original conversion with backoff.
The results of completed jobs remain available for approximately 1 hour. They can then expire. If you receive 404 when querying a job, resend the conversion.
The 202 is automatic and transparent — you don’t need to activate it. It only happens when all backends are saturated. Under normal conditions, you will always receive 200 directly.