Job lifecycle and errors

To better understand how the API works, it is necessary to explain how the lifecycle of a job works.

A job can have one of the following status:

Code Description
incomplete Missing information to run the job
ready The job is ready but not marked to be processed yet
queued The file is waiting in the queue for being processed
downloading The input file you provided is currently being downloaded
pending The file is waiting in the queue to be downloaded
processing The file is currently being converted
completed The file has been successfully converted
failed The file has not been converted due to errors

Usually, the focus will be on jobs with a completed or failed status.

When the job has been completed, you can follow the instructions to download the result

In case of a failed job, you will get a failed status. It will furthermore have an errors key, where you can find a more detailed messages on what caused the job to fail. It should look similar to this:

    ... extra information ...
    "status": {
        "code": "failed",
        "info": "The file has not been converted due to errors."
    "errors": [
            "source": "input",
            "id_source": "bc6eb7a7-8c3b-49fe-9216-0eedb2e32361",
            "code": 17,
            "message": "File not found, reasons for this error could be: bucket has incorrect permissions, you sent invalid credentials, or the file is really not there"
    "process": true,
    ... extra information ...

results matching ""

    No results matching ""