Answer a hold
Sends the answer of a person to a hold of a run. Only the credential that started the run can send it. The answer comes at the next stop of the run, or at the end of the wait: Prefer: wait=N (1 to 90), default 30 seconds. A run that ended gives 409 not_waiting. Needs the scope machines.
Authentication
An API key (crk_), an exchanged token (crt_) or a JWT of a trusted issuer. The credential needs the scope of the capability. Read the description of each route.
Path parameters
The run id. It is also the job id: job_ and a ULID.
Headers
wait=N (1 to 90) holds the request up to N seconds. respond-async answers 202 at once. Behind a proxy with a 60 second idle timeout, use wait=55 or less.
Query parameters
The alias of Prefer: wait=N. The Prefer header wins when both are there.
Request
The seq of the hold.
The answer. It must match the schema of the hold.
Response headers
The id of the request: req_ and a ULID. Every answer has it.
Response
What the run waits for: tool outputs, the answer of a person, or an input. Send it with the route of its type.