---
title: "A three-process desktop's Stop that no context carried"
method: POST
path: "/v1/recordings/{id}/stop"
tags: ["pipeline"]
---

# A three-process desktop's Stop that no context carried

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

## Request

- Base URL: `https://api.sixminute.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://api.sixminute.ai/v1/recordings/{id}/stop`
- Auth: HTTP bearer

A three-process desktop's route, kept until the follow-up removes it: answered 204 and otherwise ignored. There is no recording in the cloud; capture is a state of the device, and the cloud replays no clock step.

## Path parameters

- `id` string, required

## Request body

- object
  - `after_seq` integer, required
  - `at` string, date-time, required
  - `reason` 'person' | 'quit' | 'update' | 'sign-out' | 'roll', required

## Response `204`

Taken; nothing changes.

## Other responses

- `400`: The body, query or path did not validate; `errors` lists the fields.
- `401`: No bearer token, or one that does not verify or has expired.
- `403`: The token verified but may not do this: no organisation, not provisioned, wrong role, or a device problem.

---

[API](https://skmtc.dev/sixminute/apis/sixminute-api.md) - [All operations](https://skmtc.dev/sixminute/apis/sixminute-api/llms.txt) - [OpenAPI document](https://skmtc.dev/sixminute/apis/sixminute-api/revisions/605577eadc10?raw)