Log API
Updated at：2025-10-20
Log API
API description
Retrieve the log records associated with the command execution.
Request structure
Plain Text
1POST /v1/ca/logRequest headers
There are no special headers required beyond the common headers.
Request parameters
| Parameter name | Types | Required or not | Parameter location | Description |
|---|---|---|---|---|
| runId | String | Yes | RequestBody | Execution ID |
| childId | String | Yes | RequestBody | Sub-execution ID under an execution ID |
| cursor | int | Yes | RequestBody | The initial request is 0. For subsequent pagination, fill in the nextCursor responded upon the previous request |
Response headers
There are no special headers required beyond the common headers.
Response parameters
| Parameter name | Types | Description |
|---|---|---|
| requestId | String | Request ID |
| code | String | Response state, where successful execution is indicated by success. |
| result | LogResult | Return to the log result |
Request example
JSON
1POST /v1/ca/log
2{
3 "runId": "r-KJoCY9kKa9******",
4 "childId": "d-ks3GQL******",
5 "cursor": 0
6}Response example
JSON
1{
2 "requestId": "aaf4bd8f-ed6c-481b-ad1a-a4c974******",
3 "code": "success",
4 "result": {
5 "logs": [
6 {
7 "msg": "pwd \n",
8 }, {
9 "msg": "second line",
10 }
11 ],
12 "nextCursor": 2,
13 "state" : "RUNNING"
14 }
15}Appendix
LogResult
| Parameter name | Types | Description |
|---|---|---|
| childId | String | Sub-execution ID |
| logs | List<Log> | Log content, arranged in sequence |
| state | String | Execution status of the sub-task. Possible values: FAILED (execution failed), RUNNING (execution ongoing), SUCCESS (execution completed). |
| nextCursor | int | Cursor for the next request. If the sub-task execution has concluded and nextCursor=cursor, no further logs are available. Otherwise, additional logs may still exist. |
Log
| Parameter name | Types | Description |
|---|---|---|
| msg | String | Command execution log |