BRbrumby
simulated runs

Read Sim Batches

get/api/v1/sim-batches

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/sim-batches
  • Auth
    HTTP bearer

Query parameters

device_idstring nullable
limitinteger

Response

Successful Response

batch_idstring uuid required
namestring required
farm_idstring required
device_idstring required
dispatch'launch' | 'headless' required

How a simulated run reaches an aircraft, and therefore who authorises it.

LAUNCH is the ordinary path and the only one that flies anything: the run schedules a mission request exactly as the customer app does, a pilot signs the JSA and presses LAUNCH, and the dock delivers. FleetOps adds nothing to that sequence and skips nothing in it.

HEADLESS never asks a dock for anything. The bench composes the same mission config from the same farm and runs it against a stub dock, so there is no clearance to grant, no aircraft to arm and nothing to authorise -- which is why there is no JSA on it. A sweep of two hundred seeds is this one; a run you want a flight record for is the other.

matrixobject required
notesstring nullable required
created_bystring required
created_atstring date-time required
cancelled_atstring date-time nullable required
run_countinteger required
state_countsobject required

Changes

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