BRbrumby
mission results

Device Mission Runs

Every run of this dock, newest first: the grant ledger and the bucket.

NEITHER REGISTER IS COMPLETE. The ledger says what FleetOps authorised an upload for; the bucket says what actually landed, including the twenty-odd real runs minted by a FleetOps that is not this one. Each row says which it came from, and source=ledger is exactly the listing this endpoint used to return -- the field names and meanings of the original five are unchanged, so a client written against it keeps working.

NO DEVICE LOOKUP, on purpose. A legacy run in the bucket belongs to a dock this deployment's database may never have heard of, and refusing to show it would hide precisely the material the review tool exists to show. Nothing here is written and the prefix is derived from the path, never taken from the caller.

get/api/v1/devices/{device_id}/mission-runs

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}/mission-runs
  • Auth
    HTTP bearer

Path parameters

device_idstring required

Query parameters

limitinteger
source'ledger' | 'bucket' | 'all'

Response

Successful Response

run_idstring required
simulation_profilestring nullable
device_idstring required
media_countinteger required
outcome'granted' | 'refused' | 'uploaded' required
granted_atstring date-time nullable
completed_atstring date-time nullable
source'ledger' | 'bucket' | 'both' required
flight_idstring uuid nullable

Changes

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