Get Worker Run Log
Method: GET
Endpoint: /api/v2/worker-runs/{runId}/log
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-runs/{runId}/logGet worker run logAuthenticationRequired
Stored only in this browser tab. Sent only to https://openapi.coreclaw.com.
Parameters
Required
Run slug returned as `data.run_slug` from start or rerun responses.
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 read run logs for monitoring and troubleshooting.
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. |
Request Example
Section titled “Request Example”curl -X GET "https://openapi.coreclaw.com/api/v2/worker-runs/YOUR_RUN_ID/log" \ -H "Authorization: Bearer YOUR_API_KEY"Response Example
Section titled “Response Example”{ "code": 0, "data": { "all_logs_url": "https://storage.example.com/runs/01KKDXV2G26BT7NH4ZQR2R4NPZ/logs.txt", "list": [ "Run started", "Run finished" ], "result_count": 1 }, "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 |