List Worker Runs
Method: GET
Endpoint: /api/v2/worker-runs
Authentication: Supports Authorization: Bearer <YOUR_API_KEY>, api-key: <YOUR_API_KEY>, and ?token=<YOUR_API_KEY>. Prefer Bearer token.
Try it
Section titled “Try it”GET
/api/v2/worker-runsList worker runsAuthenticationRequired
Stored only in this browser tab. Sent only to https://openapi.coreclaw.com.
Parameters
Optional
Pagination offset, starting from 0. Constraints: default `0`; minimum 0.
Optional
Page size. Constraints: default `20`; range 1-100.
Optional
Worker slug or path. You may paste `owner/name`; the playground sends it as `owner~name` for query values.
Optional
Run status filter. Constraints: allowed values: `ready`, `running`, `succeeded`, `failed`, `aborting`.
Request BodyNot applicable
No JSON request body. Fill the path or query parameters above.
When to use this endpoint
Section titled “When to use this endpoint”Use this endpoint to list Workers available to the authenticated user.
Identifier Notes
Section titled “Identifier Notes”workerId/worker_idaccepts a Worker slug or a path encoded asowner~namefromowner/name.
Query Parameters
Section titled “Query Parameters”| Parameter | Required | Type | Description |
|---|---|---|---|
offset | No | integer | Pagination offset, starting from 0. Use it for result previews, list paging, or choosing a result window. Constraints: default 0; minimum 0. |
limit | No | integer | Page size. limit is capped at 100 on list and result endpoints. Constraints: default 20; range 1-100. |
worker_id | No | string | Worker slug or path. You may paste owner/name; the playground sends it as owner~name for query values. |
status | No | enum: ready, running, succeeded, failed, aborting | Run status filter. Constraints: allowed values: ready, running, succeeded, failed, aborting. |
Request Example
Section titled “Request Example”curl -X GET "https://openapi.coreclaw.com/api/v2/worker-runs?offset=0&limit=20&worker_id=YOUR_WORKER_ID&status=running" \ -H "Authorization: Bearer YOUR_API_KEY"Response Example
Section titled “Response Example”{ "code": 0, "data": { "count": 1, "list": [ { "duration": 10, "err_msg": "", "finished_at": 1782091210, "origin": "openapi", "results": 1, "scraper_slug": "demo-worker", "scraper_title": "Demo Worker", "slug": "01KKDXV2G26BT7NH4ZQR2R4NPZ", "started_at": 1782091200, "status": "running", "traffic": 0, "usage": "1.00", "version": "latest" } ], "page_index": 1, "page_size": 20 }, "message": "success", "request_id": "req-123"}- API v2 supports Bearer token, the legacy
api-keyheader, and query token. Prefer Bearer token for new integrations.
HTTP Responses
Section titled “HTTP Responses”| HTTP Status | Application Code | Meaning |
|---|---|---|
200 | 0 | OK |
400 | 11000 | Bad Request |
401 | 12001 | Unauthorized |
404 | 11004 | Not Found |
422 | 11000 | Unprocessable Entity |
429 | 13000 | Too Many Requests |
500 | 10000 | Internal Server Error |