DJI Integration Overview
UTMOS Open Platform supports DJI docks and drones through a unified API. This section explains the two main flows — cloud commands and device requests — and how to pick the right capability.Downlink (Cloud → Device)
Uplink (Device → Cloud)
Downlink Essentials
- Create command:
POST /api/v1/open/downlink/commands - Query result:
GET /api/v1/open/downlink/commands/{commandId}
Closure Flow
- Call the create-command endpoint; the platform returns a
command_id(a globally unique UUID). - The platform dispatches the command asynchronously over the DJI link.
- Once the device responds, the same
command_idquery endpoint returnsstatusandvendor_response.
Authentication
- API ID + API Key + request signature (see Authentication & Signing)
- Scopes:
open:command:create(create commands),open:command:read(query commands),open:device-request:read(query device requests),open:device-request:create(reply to device requests)
Request Body
| 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 |
| timeout_seconds | integer | no | Timeout in seconds (0~300) |
Query Response Fields
| Field | Type | Description |
|---|---|---|
| command_id | string(uuid) | Command acceptance identifier |
| status | string | ACCEPTED / DELIVERED / SUCCEEDED / FAILED / TIMED_OUT / UNMATCHED_RESPONSE |
| response_code | string | Device-side response code |
| response_message | string | Device-side response message |
| vendor_response | object | Raw vendor-extended response |
Capability Domains
| 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 |
| psdk | 10 | Payload and megaphone interaction, custom data channels |
| safety | 5 | Geofences, no-fly lifts, licenses, and safety policy |
| live | 4 | Live streaming start/stop, quality, and lens switching |
| file | 4 | File / media upload and transfer flow |
| firmware | 1 | Firmware OTA task creation |
Next Steps
- Downlink integration: open DJI Downlink Command Methods in the sidebar and pick a capability domain.
- Uplink request inspection: see DJI Device Requests.
- Uplink business reply: see DJI Device Request Replies.