---
title: "Read Device Flight Mission"
method: GET
path: "/api/v1/devices/{device_id}/flight-mission"
tags: ["device flight telemetry"]
---

# Read Device Flight Mission

`GET /api/v1/devices/{device_id}/flight-mission`

## 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/v1/devices/{device_id}/flight-mission`
- Auth: HTTP bearer

The mission the dock last downloaded from the aircraft (up to ~60 KB).

A sibling of `/flight-telemetry` rather than a field on it: the instruments poll
every second and the route only changes when the aircraft's mission does.

## Path parameters

- `device_id` string, required

## Response `200`

Successful Response

- DeviceFlightMissionResponse: One device's latest downloaded aircraft mission, for the ops map's route. `mission` is the dock's `mission.json` v1 verbatim (positional items). The read carries no live verdict: the console draws it only while flight telemetry is live and its `mission.total` matches this document's `total`.
  - `device_id` string, required
  - `observed_at` string, date-time, required
  - `received_at` string, date-time, required
  - `generated_at` string, date-time, required
  - `mission` object, required

## 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)