Kill Switch Endpoints

🔒 Authentication

Endpoints in this group (4 total)

GET /api/v1/kill-switch

Returns current kill-switch state — whether trading is halted, the reason, and when it was activated.

Logic Flow

200 OK example:

{
  "is_active": true,
  "reason": "Unexpected drawdown spike — manual halt",
  "activated_at": "2026-05-16T14:30:00Z",
  "activated_by": "manual"
}

POST /api/v1/kill-switch/activate

Immediately halts all automated trading. All future scheduler jobs will check is_active and skip execution.

Request body:

{
  "reason": "High-impact news event — NFP release"
}

Effect on scheduler: Every scheduled analysis job checks the kill-switch at the start. If is_active=True, the job returns early without calling MT5 or LLM.

POST /api/v1/kill-switch/deactivate

Re-enables automated trading. Next scheduled run will proceed normally.

Request body: None required.

GET /api/v1/kill-switch/logs

Returns chronological list of kill-switch events (activations + deactivations).

200 OK example:

[
  {
    "id": 5,
    "action": "activate",
    "reason": "Manual halt",
    "timestamp": "2026-05-16T14:30:00Z"
  },
  {
    "id": 6,
    "action": "deactivate",
    "reason": null,
    "timestamp": "2026-05-16T16:00:00Z"
  }
]

Pydantic Schema: backend/api/routes/kill_switch.py :: KillSwitchLogResponse

🗂️ Related Files

🗂️ Related