Skip to main content
POST
Update collaboration result
Submit only when task_state=2. Use the collaboration task id as file_task_id. See Human collaboration for ordinary fields, table structure, and verification after submission.

Authorizations

X-API-KEY
string
header
required

Production API Key. You can find it under My API in the ADP platform. Make sure the API Key is active and belongs to the production environment.

Path Parameters

tenant_name
string
default:laiye
required

Tenant name. Default: laiye.

Body

application/json
file_task_id
string
required

Collaboration task primary ID: data.metadata.collaboration_task_id from asynchronous extraction or data.id from task details. This is not task_number, the extraction task_id, or data_id.

collaboration_result
object[]
required

Existing fields to confirm or correct. Submit valid fields with explicit values only for a task in task_state=2. Submission completes the task.

Response

Business response. Check code and read business state back after writes.

code
string

Business result code. Success is success; failures may use server_error, http_server_error, or other strings. Always check this field, including for HTTP 200.

message
string
tips
string | null
data
object | null