Returns a paginated list of Operations belonging to a specific Operation List within a Pipeline. Use it to see all the individual operations queued or defined under one Operation List.
Supports filtering by operation_type, and returns a count plus previous/next pagination links alongside the Operation records.
This is the Pipelines Operations endpoint. Use the Operations API for command operations (dispatch commands).
About Operations
Esper's Pipelines system orchestrates multi-step device operations. A Pipeline contains Stages, and each Stage can have Target Lists (Targets and/or Device Groups) and Operation Lists; an Operation List groups the individual Operations that get executed as part of a Stage. Pipeline Runs, Stage Runs, and Target Runs track execution against these definitions, with statuses including PENDING, QUEUED, PROCESSING, RUNNING, WAITING, COMPLETE, SUCCESS, FAILURE, CANCELLED, TIMEOUT (default 21 days), and INVALID.
Key Fields / Query Parameters
- operationlist_id — path parameter identifying the Operation List
- operation_type — optional query filter to return only operations of a specific type
Common Use Cases
- Reviewing the individual operations configured under a Pipeline's Operation List before or after a run
- Auditing an Operation List's contents when troubleshooting a Pipeline Run
- Mock serverhttps://api.esper.io/_mock/openapi/pipelines/v0/operationlists/{operationlist_id}/operations/
- https://develop-api.esper.cloud/apihttps://develop-api.esper.cloud/api/pipelines/v0/operationlists/{operationlist_id}/operations/
curl -i -X GET \
'https://api.esper.io/_mock/openapi/pipelines/v0/operationlists/{operationlist_id}/operations/?operation_type=string' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>'{ "code": 0, "message": "string", "content": { "count": 0, "previous": "string", "next": "string", "results": [ … ] } }