Resolve a turn

POST /v1/sessions/{session_id}/turns/{turn_id}/resolve When the agent requires tool-use results during execution, this endpoint accepts the tool results and lets the agent continue processing.

Path parameters

Parameter	Type	Description
`session_id`	string	Session ID with the `sess_` prefix
`turn_id`	string	Turn ID with the `turn_` prefix

Headers

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

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

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

Response

Current state

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

Expected success response (200 OK)

When the feature ships, the endpoint is expected to return the updated turn state or an empty response.

Errors

HTTP	Type	Trigger
400	`invalid_request_error`	Malformed request
401	`authentication_error`	PAT 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.

​Path parameters

​Headers

​Request body (expected)

​Example request

​Response

​Current state

​Expected success response (200 OK)

​Errors