Submit client-side tool execution results
POST/api/v1/llm/submit-client-tool-results
Submits results for client-side tool calls and returns without waiting for the next generation segment. While the conversation still identifies a run, workflow validation rejects unmatched calls with 400 and already-resolved calls with 410.
If no active run is recorded, this call can succeed without applying any results. Reconcile stored run and tool state before treating HTTP success as confirmation that the results were applied.
A run can request further batches. Read pending client tools, execute each new batch and submit its results until the run reaches a terminal outcome. An unknown status requires reconciliation with a bounded wait, not an assumption of success. See Messages and run outcomes for outcome handling and the synchronous client-tool loop.
The following access conditions are preserved as declared intent and are not implemented by generated code: Authorized scoped domain action.
Request
Responses
- 200
Client tool results submitted
Return a result for a pending client tool call; use its actual ID, name and expected result shape.
Section ID: DOC-MA-conversations-api-submitClientToolResults#example-conversations-submitClientToolResults-request
Request example
{
"conversationKey": "example_123",
"results": [
{
"toolCallId": "tool_call_123",
"toolName": "lookup_booking",
"resultJson": {
"bookingStatus": "confirmed"
}
}
]
}
Illustrative response shape; omitted default fields and actual outcomes depend on the operation.
Section ID: DOC-MA-conversations-api-submitClientToolResults#example-conversations-submitClientToolResults-response
Response example
{
"runId": "example_123"
}
Document ID: DOC-MA-conversations-api-submitClientToolResults. Section identities and revisions.
| Section | Stable reference |
|---|---|
| Submit client-side tool execution results | DOC-MA-conversations-api-submitClientToolResults#overview |
| Request | DOC-MA-conversations-api-submitClientToolResults#request |
| Responses | DOC-MA-conversations-api-submitClientToolResults#responses |