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

# Submit Session Followup

`POST /v1/store/chat-sessions/{chat_session_id}/followup`

HTTP twin of the ``session_followup`` socket handler, for detached runs.

Queues a user turn and wakes the drain loop without a socket. The
synchronous 202 replaces the socket ack, so a detached client cannot lose
an ack under burst the way a socket emit can. Dedupe lives inside
``persist_and_announce_queued_followup``; a replayed ``call_id`` returns
the original id without a second row.

## Path parameters

- `chat_session_id` string, required

## Request body

- SessionFollowupRequest
  - `message` string, required
  - `display_message` string, nullable
  - `call_id` string, nullable
  - `gen_args` object, nullable

## Response `202`

Successful Response

- unknown

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.net/quadrillion/apis/quadrillion-cloud-api.md) · [All operations](https://skmtc.net/quadrillion/apis/quadrillion-cloud-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/quadrillion/quadrillion-cloud-api/revisions/c53108d35a70/schema)