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

# Read Device Flight Telemetry

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

## 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-telemetry`
- Auth: HTTP bearer

## Path parameters

- `device_id` string, required

## Response `200`

Successful Response

- DeviceFlightTelemetryResponse: One device's latest flight snapshot, for the pilot's live instruments. No verdict: every block carries its own `observed_at`, and `generated_at` is this server's clock at the read, so a console ages each block against the server's clock rather than its own. The instruments dim at seconds, where a laptop clock a second out would otherwise decide what reads as live.
  - `device_id` string, required
  - `received_at` string, date-time, required
  - `generated_at` string, date-time, required
  - `snapshot` 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)