BRbrumby
mission requests

Create Mission Request From Intent

THE TESTING DOOR: intent in, a canonical mission request out.

The profile is decided here from the device and the caller, the world from the profile (the customer's own data for a rehearsal, FleetOps' cache otherwise), and the mission by the one builder. A refusal names what could not be resolved.

post/api/v1/mission-intents

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-intents
  • Auth
    HTTP bearer

Headers

Idempotency-Keystring nullable

Request body

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

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.