Each file conversion workflow (from uploading the input file to downloading the output result), is performed by a job. Each job consists of several tasks. In other words, each request sent to the API endpoints is considered a unique task, which is itself a child of a job.
The workflow below illustrates how a simple JPG to WEBP conversion (job) consists of different tasks:
Job A (JPG to WEBP Conversion Workflow) Task A1 (Upload JPG) Task A2 (Convert to WEBP) Task A3 (Generate URL) Task A4 (Download WEBP from Generated URL)
It is usual that each convert job begins with an upload task and ends with a download task. Processing tasks such as the convert task often lie in the middle. Each task gets and returns data with a specific structure for its request and responses.