Errors & warnings

The API uses standard HTTP status codes, returns a JSON error body on failures, and surfaces per-item problems inside the job as errors and warnings.

HTTP status codes

Code	Meaning
200	OK — successful GET/PATCH.
201	Created — successful POST.
204	No content — successful DELETE, or empty list.
400	Bad request — invalid JSON, missing field, or a target your key may not use.
401	Unauthorized — missing or invalid API key/token.
402	Payment required — contract limit/quota exceeded.
404	Not found — unknown job/conversion/input/output id.
409	Conflict — invalid status transition (e.g. modifying a running job).
429	Too many requests — concurrent-conversion limit reached.
500	Server error.

Error body

{ "code": 400, "message": "Invalid input" }

Job-level errors & warnings

Even a successful request can produce per-input or per-conversion problems. These appear in the job's errors and warnings arrays:

"errors": [{
  "source": "input",
  "id_source": "<input-id>",
  "code": 404,
  "message": "The file could not be downloaded"
}]

Use the fail_on_input_error and fail_on_conversion_error job flags to decide whether such problems fail the whole job or are reported as warnings while the rest proceeds.

Error & warning codes

Codes the API can place in a job's errors and warnings arrays (the code field of each UserError/UserWarning).

Download & remote-input errors

Cloud upload errors

Local upload errors

Proxy errors

Conversion errors

Conversion warnings