---
title: "Dispatch Abort"
method: POST
path: "/api/dispatch/abort"
---

# Dispatch Abort

`POST /api/dispatch/abort`

## Request

- Base URL: `https://api.brumby.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.brumby.com/api/dispatch/abort`
- Auth: none declared

Service-to-service: send a MISSION_ABORT to the Jetson running the named
command. It only ends a flight. Nothing in the customer backend calls it any
more; the farm recall through FleetOps is the abort that reaches the Cube.

Auth: X-Mission-Dispatch-Token.

Resolution: device_id wins if provided; otherwise farm_id routes to the
farm's connected device. Refuse unscoped aborts so a malformed request
cannot broadcast across farms or environments.

## Headers

- `X-Mission-Dispatch-Token` string, nullable

## Request body

- DispatchAbortRequest
  - `device_id` string, nullable
  - `farm_id` integer, nullable
  - `command_id` string, nullable
  - `reason` string, nullable

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

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