Resolve a turn - Qoder CN

When an agent requires tool call results (tool use) during execution, submit the tool execution results through this endpoint so the agent can continue processing. This endpoint is not currently enabled (returns 404). It may be an M3-gated feature or will be implemented in a future release.

Request headers

Header	Required	Description
`Authorization`	Yes	`Bearer`
`Content-Type`	Yes	`application/json`

Path parameters

Parameter	Type	Required	Description
`session_id`	string	Yes	Session ID (`sess_` prefix)
`turn_id`	string	Yes	Turn ID (`turn_` prefix)

Request body (expected)

Field	Type	Required	Description
`tool_results`	array	Yes	List of tool execution results
`tool_results[].tool_use_id`	string	Yes	Corresponding tool_use ID
`tool_results[].content`	string	Yes	Result content returned by the tool

Example request

HELPCODEESCAPE-bash
curl -X POST "https://api.qoder.com.cn/api/v1/cloud/sessions/sess_019e392c0d1e74e095d21ea4c6b41def/turns/turn_019e392c0d787ceea6bb62943f9ac3ec/resolve" \
  -H "Authorization: Bearer $QODER_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "tool_results": [
      {
        "tool_use_id": "toolu_abc123",
        "content": "Tool execution result data"
      }
    ]
  }'

Current status

This endpoint returns HTTP 404 (plain text 404 page not found), indicating the route is not yet registered.

Expected success response

HTTP 200 OK When the feature ships, the endpoint is expected to return the updated Turn state or an empty response.

Errors

HTTP	type	Condition
400	`invalid_request_error`	Malformed request
401	`authentication_error`	PAT is invalid or expired
404	`not_found_error`	Session or Turn does not exist / route not implemented
409	`conflict_error`	Turn is not in a state awaiting tool results

See Errors for the full error envelope.

​Request headers

​Path parameters

​Request body (expected)

​Example request

​Current status

​Expected success response