Pipelines is an imager200’s feature that allows chaining several operations. Suppose you have a recurring task in which you have to resize, compress and grayscale an image. Without pipelines, you would have to make 3 distinct API calls and wait for the result of each call to make the next one. If the number of operations you need to execute gets larger, this can quickly become a performance bottleneck. Pipelines aims to simplify this process by allowing you to chain several operations that will be executed in one API call. A pipeline can be defined as a set of operations followed by one post operation. Because a pipeline may take some time to execute (depending on the number of operations), only async mode is supported. In order to get the image delivered after the end of the execution, a pipeline needs a post operation in its configuration. Like other imager200 endpoints, the pipeline endpoint can be called using both POST and GET methods. A POST request expects the image to be in the body while a GET expects a url parameters that points to a valid image location. More details about the pipelines endpoints can be found in the API docs. Once a pipeline is submitted, a link that allows checking its status is sent in the response. The link returns the status of the pipeline execution:

{
    "status": "finished",
    "name": "test1642377934",
    "success": true
}

a pipeline status can be either in progress or finished.