English
Business Flow Completion/Rejection
About 131 wordsLess than 1 minute
2026-01-19
Description
Business flow completion/rejection operation.
Request Specification
Method: POST + application/json
Endpoint: https://${cloud domain}/cgi/crm/v2/special/object/businessFlowComplete?thirdTraceId=${Random String}
Headers: Refer to Common Parameters
Request Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| data | Map | Yes | Data map |
| taskId | String | No | Task ID |
| approvalResult | String | Yes | Operation type: agree/reject |
| opinion | String | Yes | Comment content |
Request Example
{
"data": {
"approvalResult": "agree",
"taskId": "taskId",
"opinion": "tongyi"
}
}Response Parameters
| Parameter | Type | Description |
|---|---|---|
| traceId | string | Unique request ID |
| errorDescription | string | Error description |
| errorMessage | string | Error message |
| errorCode | Int | Error codes reference |
Response Example
{
"traceId": "E-O.827xxxxxx",
"errorDescription": "success",
"errorMessage": "OK",
"errorCode": 0
}Notes
- Do not use the message field in the response for logical judgment as errorMessage may change;
