BRbrumby
flights

Device Current Flight

The open flight with its track tail.

track_after makes the 5 s poll incremental: pass the ts of the last point already held and only newer points come back. A null body means no flight is open — a fact, not an error.

get/api/v1/devices/{device_id}/flights/current

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}/flights/current
  • Auth
    HTTP bearer

Path parameters

device_idstring required

Query parameters

track_afterstring date-time nullable

Response

Successful Response

flight_idstring uuid required
device_idstring required
boot_idstring uuid required
aircraft_idstring nullable required
farm_idstring nullable
installation_idstring uuid nullable
mission_request_idstring uuid nullable
mission_idstring nullable
requested_bystring nullable
launched_bystring nullable
mission_config_sha256string nullable
attribution_sourcestring nullable
customer_schedule_idinteger nullable
requested_by_account_idinteger nullable
started_atstring date-time required
ended_atstring date-time nullable required
outcome'in_progress' | 'completed' | 'recalled' | 'interrupted' | 'unknown' | 'sim_ended' required

How a materialized flight ended.

unknown is honest, not lazy: operations went stale mid-flight, so the dock-side truth was never observed. interrupted is a dock reboot while the flight row was open. sim_ended is a SIMULATED flight whose simulation was ended -- by the operator, a failure, or a runner that stopped reporting -- while the flight was open: the aircraft did not land, it stopped existing, and saying "completed" or "unknown" would each be a lie of a different kind. Only services/sim_runs.close_out writes it. No migration: enum_type is a plain String(20).

end_reasonstring nullable required
record_idstring nullable
run_idsstring[]
media_countinteger

Changes

No recorded changes to this operation across all 1 revision of this API.