Get Algo Order by Client Order ID

#Endpoint

GET /v1/algo/client/order/{client_order_id}

Mainnet: GET https://api.orderly.org/v1/algo/client/order/{client_order_id}

Testnet: GET https://testnet-api.orderly.org/v1/algo/client/order/{client_order_id}

Rate limit: 10 requests per second. Returns a single algorithmic order associated with the supplied client order ID. This signed GET request has no body.

#Authentication headers

• orderly-timestamp — signed-request timestamp in milliseconds.
• orderly-account-id — PangoPerps account ID.
• orderly-key — public API key.
• orderly-signature — request signature.

#Path parameter

#Example request

curl --request GET \
  --url 'https://api.orderly.org/v1/algo/client/order/pango-algo-001' \
  --header 'orderly-account-id: <account-id>' \
  --header 'orderly-key: <public-api-key>' \
  --header 'orderly-signature: <signature>' \
  --header 'orderly-timestamp: <timestamp-in-ms>'

#Successful response

The 200 response uses the algo-order object described in Get Algo Order by Order ID, including its trigger, execution, status, margin, and nested-child details.

{
  "success": true,
  "data": {
    "algo_order_id": 123456789,
    "client_order_id": "pango-algo-001",
    "algo_status": "NEW",
    "algo_type": "STOP",
    "is_triggered": "false",
    "quantity": 0.25,
    "side": "BUY",
    "symbol": "PERP_ETH_USDC",
    "trigger_price": 3400,
    "trigger_price_type": "MARK_PRICE",
    "type": "MARKET",
    "child_orders": []
  },
  "timestamp": 1702989203989
}