---
title: "Set Desk Trading Halt"
method: POST
path: "/v1/me/accounts/{account_id}/halt"
---

# Set Desk Trading Halt

`POST /v1/me/accounts/{account_id}/halt`

## Request

- Base URL: `https://api.quantradin.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.quantradin.com/v1/me/accounts/{account_id}/halt`
- Auth: none declared

THE DESK KILL SWITCH (Wave A) — stop (or resume) every bot on one
desk. Session-owner scoped; 404 if the desk is not the caller's (cloak).

`{"halted": true, "reason": "..."}` stops every bot on the desk from
OPENING anything, whatever its own spec or verdict says.
`{"halted": false}` resumes and CLEARS the reason (a stale reason left
lying around reads as a current one).

IT STOPS ENTRIES ONLY, and that is the design, not a softening. Open
positions keep being marked and keep exiting on their stops. A kill
switch that also froze the exits would leave a member unable to get OUT
of the thing that scared them, which is the opposite of a safety
control. Every bot reads the flag on its own next walk, so a halt takes
effect within one tick and needs no per-bot write.

## Path parameters

- `account_id` integer, required

## Request body

- TradingHaltRequest
  - `halted` boolean, required
  - `reason` string, nullable

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/quantradin/apis/vega-api.md) · [All operations](https://skmtc.dev/quantradin/apis/vega-api/llms.txt) · [OpenAPI document](https://skmtc.dev/quantradin/apis/vega-api/revisions/47add154ef38?raw)