Get Order Status (Batch)

Fetches historical order statuses for multiple orders by internal order IDs and/or client-provided order IDs. Returns execution details, settlement status, and maker match data for each order.

POST /orders/status/batch

Get order statuses in batch

cURL

curl --request POST \
  --url https://api.limitless.exchange/orders/status/batch \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <api-key>' \
  --data '
{
  "items": [
    {
      "orderId": "4aa706dd-6c57-4f3c-945a-99818dfd95f1",
      "clientOrderId": "client-order-001"
    }
  ]
}
'

200

{
  "results": [
    {
      "index": 0,
      "status": "found",
      "error": "Exactly one of orderId or clientOrderId is required",
      "orderId": "<string>",
      "clientOrderId": "<string>",
      "data": {
        "makerMatches": [
          {}
        ],
        "execution": {
          "clientOrderId": "<string>",
          "feeRateBps": 0,
          "effectiveFeeBps": 0,
          "matched": true,
          "settlementStatus": "UNMATCHED",
          "tradeEventId": "<string>",
          "txHash": "<string>",
          "totalsRaw": {
            "contractsGross": "<string>",
            "contractsFee": "<string>",
            "contractsNet": "<string>",
            "usdGross": "<string>",
            "usdFee": "<string>",
            "usdNet": "<string>"
          }
        }
      }
    }
  ]
}

Look up orders by either orderId (internal) or clientOrderId (your identifier). Provide exactly one per item — not both.

Authorizations

X-API-Key · string · header · required

API key for programmatic access. Generate at limitless.exchange -> profile menu -> Api keys.

Body

application/json

items · object[] · required

List of status lookup queries (1-50 items)

Required array length: 1 - 50 elements

Show child attributes

Response

200

application/json

Batch order statuses

results · object[] · required

Array of status results corresponding to request items

Show child attributes