Skip to content

Get all Runs for the Pipeline
Stable

Request

Lists all Pipeline Runs created for a given Pipeline.

Supports filtering by status and ordering by run_number, status, started_at, or ended_at (prefix a field with - for descending order).

About Pipeline Runs

Each time a Pipeline is executed it produces a Pipeline Run, which moves through PENDING (created) → QUEUED (queued for processing) → PROCESSING (scheduler preparing it) → RUNNING → WAITING (on a manual/automatic action) → COMPLETE (all Stage Runs processed), then SUCCESS or FAILURE. A run can also end as CANCELLED (user-cancelled), TIMEOUT (default 21 days), or INVALID (the pipeline has zero stages).

Key Fields / Query Parameters

  • status — filter by run status (pending, queued, processing, running, waiting, complete, success, failure, cancelled, invalid, timeout)
  • ordering — sort by run_number, status, started_at, or ended_at
Security
pipelines_SCAPIAuthToken
Path
pipeline_idstringrequired

ID of the Pipeline

Query
statusstring

Filter by pipeline run status

Enum:"pending""queued""processing""running""waiting""complete""success""failure""cancelled""invalid"
orderingstring

Sorting pipelines runs based on the field name

Enum:"run_number""-run_number""status""-status""started_at""-started_at""ended_at""-ended_at"
cURL
curl -i -X GET \
  'https://api.esper.io/_mock/openapi/pipelines/v0/pipelines/{pipeline_id}/runs/?status=pending&ordering=run_number' \
  -H 'Authorization: Bearer <YOUR_TOKEN_HERE>'

Responses

All Runs for the Pipeline

Bodyapplication/json
codeinteger
messagestring
contentobject
Response
{
  "code": 0,
  "message": "string",
  "content": {
    "count": 0,
    "previous": "string",
    "next": "string",
    "results": [ … ]
  }
}