Answer a question a run is waiting on. The answer is checked against the wait’s schema, recorded, and handed to the step that asked, and the turn continues.
The run’s owner answers: the signed-in person or the API key that started the run. The waitId comes from the wait.<class>.raised event on the run’s stream, which also carries the question and the schema the answer must match.
Path
runIduuidRequired
The run holding the wait.
waitIduuidRequired
The wait, from its wait.<class>.raised event.
Body
The answer itself, as JSON. What it may be depends on the wait.
WaitAnswer
Clarification
A JSON string, or { "Declined": true, "Reason": "…" } to say no.
UserLocationRequired
A JSON string naming the place.
Signal
Any JSON.
Responses
StatusBody
204
The answer was recorded. The turn continues once every wait it is holding is answered.
With Accept: text/event-stream, the response follows the run’s current turn to its end instead: an opened frame, the turn’s events, then closed.
Errors
StatusCodeWhat happened
401
—
No API key or session.
404
—
You hold no run with this id, or the run holds no wait with this id.
409
—
The wait is already answered.
410
—
The wait ended before this answer arrived: its turn was cancelled, superseded, replaced or timed out.
422
—
The answer does not match the wait’s schema. The wait stays open.