---
title: "Send Mission Control command"
method: POST
path: "/v0/mission/control"
tags: ["nvi4ncvyy029fume"]
---

# Send Mission Control command

`POST /v0/mission/control`

## Request

- Base URL: `https://api.skydio.com/api`
- URL: `https://api.skydio.com/api/v0/mission/control`
- Auth: API key in header `Authorization`

Send a Mission Control command to a given vehicle.

## Headers

- `Idempotency-Key` string: Unique value generated by the client so that the service will not execute duplicate requests on the same vehicle

## Request body

- object: Arguments to the POST /mission/control endpoint
  - `mission_control_type` 'PAUSE' | 'RESUME' | 'RETURN_AND_LAND_IN_DOCK' | 'LAND_IN_PLACE' | 'SKIP_TO_WAYPOINT', required: Mission control command to issue to the vehicle
  - `mission_template_uuid` string, uuid: ID of the mission affected by this command. This request parameter can only be used when mission_control_type is SKIP_TO_WAYPOINT. Optional when the vehicle is already flying a mission. If the vehicle is not flying, this parameter is required and will trigger the vehicle to start the mission before skipping to the correct waypoint.
  - `vehicle_serial` string, required
  - `waypoint_uuid` string, uuid: ID of the waypoint affected by this command. Required when mission_control_type is SKIP_TO_WAYPOINT.

## Response `200`

Mission Control command returned by the POST /mission/control endpoint

- object
  - `data` object, required: Mission Control command returned by the POST /mission/control endpoint
    - `mission_control` object, required
      - `idempotency_key` string: Value of the Idempotency-Key header provided in the request to the POST /mission/control endpoint. The Idempotency-Key header is optional, but is highly recommended
      - `mission_control_type` 'PAUSE' | 'RESUME' | 'RETURN_AND_LAND_IN_DOCK' | 'LAND_IN_PLACE' | 'SKIP_TO_WAYPOINT', required: Mission control command to issue to the vehicle
      - `mission_template_uuid` string, uuid: ID of the mission affected by this command. This request parameter can only be used when mission_control_type is SKIP_TO_WAYPOINT. Optional when the vehicle is already flying a mission. If the vehicle is not flying, this parameter is required and will trigger the vehicle to start the mission before skipping to the correct waypoint.
      - `sent` string, date-time: Time at which the control was sent to the vehicle
      - `vehicle_serial` string, required
      - `waypoint_uuid` string, uuid: ID of the waypoint affected by this command. Required when mission_control_type is SKIP_TO_WAYPOINT.
  - `error_message` string
  - `meta` object, required
    - `time` number
  - `skydio_error_code` integer, required
  - `status_code` integer, required

## Other responses

- `403`: You do not have permission to send mission controls.
- `404`: Not Found
- `409`: Vehicle is offline.

## Changes

- **2026-11-03** `6589167ebe70`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/skydio/apis/skydio-cloud-api/changes/v0/mission/control/post.md)

---

[API](https://skmtc.dev/skydio/apis/skydio-cloud-api.md) - [All operations](https://skmtc.dev/skydio/apis/skydio-cloud-api/llms.txt) - [OpenAPI document](https://skmtc.dev/skydio/apis/skydio-cloud-api/revisions/6589167ebe70?raw)