---
title: "stop session"
method: POST
path: "/v1/sessions/{id}/stop"
tags: ["Sessions"]
---

# stop session

`POST /v1/sessions/{id}/stop`

Force-terminates a running session. The engine hosting the session
disconnects the client and shuts the session down immediately.

Termination is asynchronous on the engine side: the session's
`endTime`, exit status and session report are delivered through the
normal end-of-session flow shortly after the stop, so the session may
briefly still appear active on `GET /v1/sessions/{id}`.

Sessions that never reached an engine, or that run over the LiveKit
or Agora integrations, have no engine host to terminate and return
`404`. If the engine rejects the stop (for example the session has
already ended), the engine's error status is passed through.

## Path parameters

- `id` string, uuid, required

## Response `200`

The engine accepted the stop request

- object

## Other responses

- `400` — Bad request - Invalid session ID
- `401` — Unauthorized - Invalid or missing API key
- `403` — Forbidden - API key lacks the required permission
- `404` — Not Found - Session not found, or it has no engine to terminate (it never reached an engine, or is a LiveKit/Agora session)
- `500` — Server error

---

[API](https://skmtc.net/anam/apis/anam-ai-api.md) · [All operations](https://skmtc.net/anam/apis/anam-ai-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/anam/anam-ai-api/versions/67afd1c5db59/schema)