Answer a question the agent asked

Records what the person chose for one ask_user call and releases the tool call that has been blocked on it.

One answer per question, in the order the questions were asked. The indices are into the option list exactly as question-asked sent it — the engine ordered those options, so a client that reordered them would send back the wrong choice. Answering a question that is already answered, or one a host closed when its turn was interrupted, is a conflict: the tool it was blocking is no longer waiting.

A question is not a permission and this is not decidePermission: no rule can be written about a question, nothing is remembered, and the decision audit never carries one.

On a product session nothing is blocked: the ask_user call finished when it asked and its turn ended there, and the question stands, a restart included, until it is answered here or the person sends a message on its lane instead, which closes it. Answering it starts the next turn with the answer as the person’s message, called as this request’s person; the 204 is that turn accepted, and a refusal to admit it answers as createMessage would. The message rides the question’s id as its idempotency key, so answering again after a refusal, or a second press, sends the recorded answer once rather than answering 409. A refusal that leaves no message behind reopens the question and answers 409 NRY-0032 instead of the message road’s own status: the answer was not delivered and the question is pending again, which a client must not read as the question being settled.

POST /v1/questions/{questionId}/answer

Answer a question the agent asked

cURL

curl --request POST \
  --url https://api.example.com/v1/questions/{questionId}/answer \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "answers": [
    {
      "options": [
        0
      ]
    },
    {
      "options": [
        2
      ],
      "text": "Keep both and reconcile nightly."
    }
  ]
}
'

400

{
  "code": "NRY-0002",
  "title": "Session not found",
  "message": "No session with id 6b9f6d2e-1c3a-4f5b-9d7e-2a8c4e6f0b1d exists on this host."
}

Autorizações

Authorization · string · header · obrigatório

Enforced on every transport, with no exempt operation. A person's request must carry a JWT issued by the configured identity provider, which the host verifies itself against that issuer's key set: signature, issuer, expiry, and the person and organisation it names. Requests without a valid one receive 401 NRY-0011 — except a request with no token on a laptop's socket from the OS user the kernel names as the host's own, which is that machine's user.

Parâmetros de caminho

questionId · string<uuid> · obrigatório

The question's id, as question-asked announced it.

Corpo

application/json

One person's answer to every question of one ask_user call, in the order the questions were asked — position is the join, because a question carries no id of its own.

answers · object[] · obrigatório

One entry per question asked, in that order.

Required array length: 1 - 4 elements

Show child attributes

Resposta

204

Answered. On a session with a blocked tool call, that call is running again, and its close arrives as tool-call-finished for the call question-asked named. On a product session nothing was blocked: the answer is the person's message, and this 204 is the next turn accepted.