GET
/
api
/
v1
/
open
/
downlink
/
commands
/
{command_id}
Get a downlink command
curl --request GET \
  --url https://api.example.com/api/v1/open/downlink/commands/{command_id} \
  --header 'X-Api-Id: <x-api-id>' \
  --header 'X-Api-Nonce: <x-api-nonce>' \
  --header 'X-Api-Signature: <api-key>' \
  --header 'X-Api-Timestamp: <x-api-timestamp>'
{
  "command_id": "100e2826-e45b-50cb-b41f-e8df6d20bea2",
  "status": "ACCEPTED",
  "vendor": "dji",
  "device_id": "drone-001",
  "command_type": "camera_photo_take",
  "timeout_seconds": 30,
  "accepted_at": "2026-04-22T12:00:00Z",
  "dispatch_status": "PENDING",
  "publish_attempts": 0,
  "published_at": null,
  "last_error": null,
  "request_id": "req-001"
}

Authorizations

​
X-Api-Signature
string
header
required

HMAC signature; X-Api-Id, X-Api-Timestamp, and X-Api-Nonce are also required.

Headers

​
X-Api-Id
string
required

API credential ID.

​
X-Api-Timestamp
string
required

Unix timestamp in seconds.

​
X-Api-Nonce
string
required

Replay-protection nonce.

​
X-Api-Signature
string
required

HMAC request signature.

​
X-Request-Id
string

Optional correlation ID.

Path Parameters

​
command_id
string
required

Command ID

Response

Command fact and dispatch state.

​
command_id
string<uuid>
required
​
status
enum<string>
required
Available options:
ACCEPTED,
DISPATCHING,
DELIVERED,
RUNNING,
SUCCEEDED,
FAILED,
TIMED_OUT,
UNSUPPORTED,
CANCELLED,
UNKNOWN
​
vendor
string
required
Example:

"px4"

​
device_id
string
required
​
command_type
string
required
​
timeout_seconds
integer
required
​
accepted_at
string<date-time>
required
​
dispatch_status
enum<string>
required
Available options:
PENDING,
PUBLISHED,
FAILED,
DEAD
​
publish_attempts
integer
required
​
request_id
string
required
​
public_status
enum<string>
required
Available options:
ACCEPTED,
DISPATCHING,
DELIVERED,
RUNNING,
SUCCEEDED,
FAILED,
TIMED_OUT,
UNSUPPORTED,
CANCELLED,
UNKNOWN
​
published_at
string<date-time> | null
​
last_error
string | null
​
adapter_result
object

Terminal adapter or device result. command accepted does not mean device execution succeeded; callers should rely on this result or callbacks.