​
DJI Services · drc

​
001 Capability Boundary

001 currently supports accepting DJI DRC /services methods through the unified HTTP command API. The platform persists the command fact, creates a dispatch event, and returns command_id. Low-latency DRC WebSocket, joystick control, emergency-stop heartbeat channels, and device-side execution are later realtime / DJI adapter capabilities. This page describes only the DRC methods included in the 001 command catalog and how to submit them through the HTTP entry point.

​
API Entry Points

OperationMethod and path
Create commandPOST /api/v1/open/downlink/commands
Query command factGET /api/v1/open/downlink/commands/{commandId}

​
Authentication And Scope

  • API ID + HMAC request signature
  • Create command: open:command:create
  • Query command: open:command:read

​
Flow

  1. Call the create-command endpoint with vendor=dji, command_type, and the method payload.
  2. The platform returns command_id and ACCEPTED.
  3. The platform persists the command fact and dispatch event, then attempts to publish command.accepted.
  4. Query by command_id to read the accepted command fact and dispatch publication state.

​
Status Model

StatusDescription
ACCEPTED001 accepted and persisted the command.
DELIVEREDWritten by a later adapter: command was delivered to the device side.
SUCCEEDEDWritten by a later adapter: device execution succeeded.
FAILEDWritten by a later adapter: device execution failed.
TIMED_OUTWritten by later scheduler/adapter logic: command timed out.
UNMATCHED_RESPONSEWritten by later correlation logic: a device response could not be correlated.

​
All Methods

​
Response

  • Create Response: platform acceptance state, status=ACCEPTED
  • Query Response: platform command fact and dispatch publication state; device execution terminal states require later adapter writes