Submit tool-call input
Approves or rejects one tool call the AI builder is waiting on, then resumes the turn.
Some steps pause for you before they run. The turn stops with an assistant message whose tool call has no result yet, and the builder waits. Answer it here to let the turn continue. Use Read conversation messages to find the tool call that is waiting and take its ID.
The request stays open until the resumed turn settles, so it can take several minutes. Resuming a turn consumes credits. To answer several waiting tool calls at once, use Submit tool-call input (batch).
Authorizations
Personal API key.
Path Parameters
ID of the app whose builder chat this request acts on.
Body
ID of the tool call to answer. Read it off the waiting assistant message returned by Read conversation messages.
"toolu_01A9FJd3kP2mNqRs7VwXyZ4b"
Whether to let the tool call run or turn it down. Rejecting tells the builder to continue without doing that step.
approved, rejected "approved"
ID of the message the tool call belongs to. Some tools use it to report progress.
"7f3a1c88-52d4-4a0e-9b31-2c6f0d8e4a19"
Response
The app once the resumed turn finished.
The app document the chat endpoints return once a turn settles.
The real payload is the whole app document, so this is a strict subset: the fields a caller needs to see what the turn did and whether it succeeded.
ID of the app.
"6820f3a4e7b91d003c45a1f2"
Display name of the app.
"My CRM"
The app's build status once the request returned. Read state to tell a finished turn from one that is still processing or that failed.
The app's conversation, including the messages this request produced.