DJI Cloud Commands
DJI Cloud Commands let integrators submit DJI control, task, configuration, live streaming, file, firmware, and other operation requests through Open Platform. 001 currently implements platform-side command acceptance, command fact persistence, dispatch event creation, and command query. Actual device execution is owned by a later DJI adapter service.API Entry Points
| Operation | Method and path |
|---|---|
| Create command | POST /api/v1/open/downlink/commands |
| Query command status | GET /api/v1/open/downlink/commands/{commandId} |
Flow
- Call the create-command endpoint with
vendor=dji, acommand_type, and the method-specificpayload. - The platform returns a
command_idand the acceptance statusACCEPTED. - 001 persists the command fact and dispatch event, then attempts to publish
command.accepted. - Query by
command_idto retrieve the accepted command fact and dispatch publication state. Device execution terminal states appear only after later adapter / callback / query capabilities write them.
Request Fields
| Field | Type | Required | Description |
|---|---|---|---|
| vendor | string | yes | Fixed value dji |
| device_id | string | yes | Target device ID |
| command_type | string | yes | DJI method name |
| payload | object | yes | Method payload |
| idempotency_key | string | yes | Idempotency key; keep it stable when retrying the same business request |
| timeout_seconds | integer | no | Timeout in seconds, range 0~300 |
Status Model
| Status | Description |
|---|---|
ACCEPTED | Platform accepted the command. |
DELIVERED | Written by a later adapter: command was delivered to the device side. |
SUCCEEDED | Written by a later adapter: device execution succeeded. |
FAILED | Written by a later adapter: device execution failed. |
TIMED_OUT | Written by later scheduler/adapter logic: no terminal status was received before timeout. |
UNMATCHED_RESPONSE | Written by later correlation logic: a device response could not be correlated to the command. |
Example Request
DJI Downlink Command Methods
Choose a capability domain in the sidebar to view method-specific payload fields, request examples, and response examples.| Domain | Methods | Purpose |
|---|---|---|
device | 21 | Dock/device control, maintenance, and mode switching |
camera | 17 | Camera/gimbal capture, focus, exposure, and composition |
drc | 12 | Remote-control takeover and direct flight control |
wayline | 9 | Wayline mission lifecycle and return-to-home control |
live | 4 | Live streaming start/stop, quality, and lens switching |
psdk | 10 | Payload and megaphone interaction, custom data channels |
file | 4 | File / media upload and transfer flow |
safety | 5 | Geofences, no-fly lifts, licenses, and safety policy |
firmware | 1 | Firmware OTA task creation |