Headers
-
Broker access key identifier.
Format should match the following pattern:
^[A-Za-z0-9._~-]{1,64}$. -
Keyed BLAKE2b-256 signature (hex lowercase, 64 characters).
Format should match the following pattern:
^[0-9a-f]{64}$. -
RFC3339 timestamp with milliseconds (e.g., 2025-10-30T06:00:34.075Z). Must be within clock_skew_tolerance (default 5m) of server time.
GET
/trading/accounts/{account_id}/orders/{order_id}
curl \
--request GET 'https://api.example.com/v1/trading/accounts/{account_id}/orders/{order_id}' \
--header "PRE-ACCESS-KEY: string" \
--header "PRE-ACCESS-SIGNATURE: string" \
--header "PRE-ACCESS-TIMESTAMP: 2026-05-04T09:42:00Z"
Response examples (200)
{
"order_id": "string",
"client_order_id": "string",
"market_id": "string",
"broker_id": "string",
"account_id": "string",
"side": "BUY",
"type": "LIMIT",
"tif": "GTC",
"token": "YES",
"price": {
"units": 42,
"nanos": 42
},
"qty": {
"units": 42,
"nanos": 42
},
"volume": {
"units": 42,
"nanos": 42
},
"filled_qty": {
"units": 42,
"nanos": 42
},
"filled_volume": {
"units": 42,
"nanos": 42
},
"filled_fee": {
"units": 42,
"nanos": 42
},
"status": "NEW",
"status_reason": "USER_REQUEST",
"last_update_wall_time_ns": 42,
"last_update_engine_seq": 42,
"last_cmd_id_hex": "string"
}
Response examples (404)
{
"error_code": "string",
"message": "string",
"details": {}
}
Response examples (503)
{
"error_code": "string",
"message": "string",
"details": {}
}