---
title: "Presence"
method: POST
path: "/api/v1/aircraft/presence"
tags: ["aircraft"]
---

# Presence

`POST /api/v1/aircraft/presence`

## 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/aircraft/presence`
- Auth: none declared

204 accepted; 409 a replayed or too-frequent report (the next one is fine); 401 a
token FleetOps does not hold.

## Headers

- `authorization` string, nullable

## Request body

- AircraftPresenceV1: `POST /api/v1/aircraft/presence`, every 15 s under the aircraft token: the Jetson is online because it says so. FleetOps keeps it in the docks' presence tables and applies their one online rule (`presence.ingest_presence`): `sequence` rises within a `boot_id`, and a device unheard for `offline_ttl_seconds` is offline.
  - `schema` 'brumby.aircraft-presence.v1', required
  - `boot_id` string, uuid, required
  - `sequence` integer, required
  - `observed_at` string, date-time, required
  - `hostname` string
  - `uptime_seconds` number
  - `version` string
  - `health` AircraftHealth, required: What the aircraft's Jetson says of itself. `stack`: its flight stack (brumby-air.service) runs. `fcu`, `pod`: as in its pairing result's links.
    - `stack` LinkReport, required
      - `ok` boolean, required
      - `detail` string
    - `fcu` LinkReport, required
      - `ok` boolean, required
      - `detail` string
    - `pod` LinkReport, required
      - `ok` boolean, required
      - `detail` string

## Response `204`

Successful Response

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