store

Submit Session Confirmation

Changed on

HTTP twin of the confirmation socket handlers, for detached runs.

A detached client observes status == "pending_confirmation" on its poll, reads the confirmation id and options from the durable actions log, and answers here. Command approvals resolve an in-memory future on this replica and fan out to peers via the socket-event bus, with a persisted fallback by call_id.

post/v1/store/chat-sessions/{chat_session_id}/confirmation

Request

  • Base URL
    https://api.quadrillion.io (the document declares no server; this is the origin it was published from)
  • URL
    https://api.quadrillion.io/v1/store/chat-sessions/{chat_session_id}/confirmation
  • Auth
    none declared

Path parameters

chat_session_idstring required

Request body

confirmation_idstring required
kind'command_approval' | 'question' required
actionstring nullable
call_idstring nullable
question_indexinteger nullable
responsestring nullable

Response

Successful Response

unknown required

Changes