---
title: "Submit Session Confirmation"
method: POST
path: "/v1/store/chat-sessions/{chat_session_id}/confirmation"
tags: ["store"]
---

# Submit Session Confirmation

`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

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``.

## Path parameters

- `chat_session_id` string, required

## Request body

- SessionConfirmationRequest
  - `confirmation_id` string, required
  - `kind` 'command_approval' | 'question', required
  - `action` string, nullable
  - `call_id` string, nullable
  - `question_index` integer, nullable
  - `response` string, nullable

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

## Changes

- **2026-09-18** `abf76937a751`: 2 info
  - added the optional property `detail/items/ctx` to the response with the `422` status
  - added the optional property `detail/items/input` to the response with the `422` status
- **2026-08-22** `c53108d35a70`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/quadrillion/apis/quadrillion-cloud-api/changes/v1/store/chat-sessions/:chat_session_id/confirmation/post.md)

---

[API](https://skmtc.dev/quadrillion/apis/quadrillion-cloud-api.md) - [All operations](https://skmtc.dev/quadrillion/apis/quadrillion-cloud-api/llms.txt) - [OpenAPI document](https://skmtc.dev/quadrillion/apis/quadrillion-cloud-api/revisions/2e1425e0e054?raw)