When waitpoints appear
The realtime stream emits a waitpoint event that contains awaitpointId and a prompt or question. While the waitpoint is open, the run stays in a waiting state. The run resumes only after you respond to the waitpoint or cancel the run.
If you are listening to the realtime stream, watch for an event with the waitpoint details so you can surface the prompt to the user.
Responding to a waitpoint
Send your response to the waitpoint with a single POST call. The run resumes automatically once the API receives it.Endpoint
Request body
Examples
A waitpoint is owned by the same user as its parent run. If you try to respond with a different user’s token, the API returns
404 Not Found instead of 403 Forbidden.