BRbrumby
mission requests

Create Operator Mission Request

Queue a mission from a hand-built config. It remains pending until the normal signed-JSA launch.

COMPATIBILITY DOOR. The config is read for its intent only (intent_from_legacy_config: the paddock names, a selected gate, the survey options, the frozen flight plan) and REBUILT by the canonical builder under the device's profile from FleetOps' farm data. Geometry a browser sent is never stored. New callers post intent to POST /api/v1/mission-intents.

post/api/v1/mission-requests

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

Headers

Idempotency-Keystring nullable

Request body

farm_idstring required
device_idstring required
mission_idstring required
configobject required
mission_plan_idstring uuid nullable
mission_plan_revisioninteger nullable
purpose'commercial' | 'testing'

Response

Successful Response

execution_type'deployment' | 'hitl' | 'sitl'
simulationobject nullable
request_idstring uuid required
purpose'commercial' | 'testing'
execution_profilestring nullable
originstring nullable
readinessstring nullable
schema_versionstring nullable
farm_idstring required
device_idstring nullable required
mission_idstring required
mission_plan_idstring uuid nullable
mission_plan_revisioninteger nullable
config_sha256string required
statestring required
requested_forstring date-time nullable required
requested_atstring date-time required
requested_bystring required
action_idstring uuid nullable required
decided_atstring date-time nullable required
decided_bystring nullable required
decision_notestring nullable required
flight_record_idstring uuid nullable required
stage_failedboolean required
rig_manifestobject nullable

Changes

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