List Worker Run Results
Method: GET
Endpoint: /api/v2/worker-runs/{runId}/result
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”/api/v2/worker-runs/{runId}/resultList worker run resultsStored only in this browser tab. Sent only to https://openapi.coreclaw.com.
Run slug returned as `data.run_slug` from start or rerun responses.
Page number, 1-based. `offset=1` is page 1, `offset=2` is page 2; `offset=0` is accepted as page 1. Out-of-range pages return an empty list. Constraints: default `1`; minimum 0.
Page size. Constraints: default `20`; range 1-100.
When to use this endpoint
Section titled “When to use this endpoint”Use this endpoint to read paginated result rows for previews or tables.
Identifier Notes
Section titled “Identifier Notes”runIdis the run slug. Usedata.run_slugfrom start or rerun responses as therunId.
Path Parameters
Section titled “Path Parameters”| Parameter | Required | Type | Description |
|---|---|---|---|
runId | Yes | string | Run slug returned as data.run_slug from start or rerun responses. |
Query Parameters
Section titled “Query Parameters”| Parameter | Required | Type | Description |
|---|---|---|---|
offset | No | integer | Page number, 1-based. offset=1 is page 1, offset=2 is page 2; offset=0 is accepted as page 1. Out-of-range pages return an empty list. Constraints: default 1; minimum 0. |
limit | No | integer | Page size. limit is capped at 100 on list and result endpoints. Constraints: default 20; range 1-100. |
Request Example
Section titled “Request Example”curl -X GET "https://openapi.coreclaw.com/api/v2/worker-runs/YOUR_RUN_ID/result?offset=1&limit=20" \ -H "Authorization: Bearer YOUR_API_KEY"Response Example
Section titled “Response Example”{ "code": 0, "data": { "count": 1, "headers": [ { "key": "title", "label": "Title" } ], "list": [ { "title": "Example result" } ], "page_index": 1, "page_size": 20 }, "message": "success", "request_id": "req-123"}Response Fields
Section titled “Response Fields”| Field | Type | Description |
|---|---|---|
data.count | integer | Total number of result rows for the run. |
data.headers[] | array | Column definitions; each item has key (field name) and label (display name). |
data.list[] | array | Result rows; each row keys align with headers[].key. |
Result rows may include internal fields not declared in the Worker output schema (for example
__coreclaw_data_id__); ignore them as needed. Serialization of nested or empty values depends on the export format;filter_keysmust matchheaders[].key. Page requests use 1-basedoffset(page number) andlimit(max100).
- API v2 supports Bearer token, the legacy
api-keyheader, and query token. Prefer Bearer token for new integrations. - Result lists use
offsetandlimitpagination. offsetis a 1-based page number (offset=1is page 1,offset=0is accepted as page 1);limitdefaults to20and cannot exceed100.- See Run Lifecycle & Status for status handling, polling, failure diagnosis, and cancellation behavior.
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 |