historicalOrdersByTime - Historical Orders by Time
Retrieve order status updates for one user inside a bounded time window from the Dwellir Hyperliquid Index over /info or JSON-RPC.
Use historicalOrdersByTime to retrieve order status updates for one Hyperliquid user inside a bounded time window. Results are ordered by ascending status timestamp.
Endpoints
REST-style Info API:
POST https://api-hyperliquid-index.n.dwellir.com/YOUR_API_KEY/infoJSON-RPC:
POST https://api-hyperliquid-index.n.dwellir.com/YOUR_API_KEY/jsonrpcParameters
| Field | Type | Required | Description |
|---|---|---|---|
type | string | yes | Must be historicalOrdersByTime for /info. |
user | string | yes | 0x-prefixed Hyperliquid user address. |
coin | string | no | Exact Hyperliquid market symbol, for example BTC. When supplied, only rows for that market are returned. |
startTime | number | yes, unless cursor is supplied | Inclusive Unix timestamp in milliseconds. Skipped when cursor is supplied. |
endTime | number | no | Exclusive Unix timestamp in milliseconds. |
cursor | string | no | Pagination cursor in statusTimestamp_txIndex_oid format. Resumes after that order status update. |
limit | number | no | Maximum rows to return, capped at 2000. |
Billing
Billed by returned order objects
historicalOrdersByTime responses are billed by the number of order status objects returned, not as one response per HTTP request.
A response with 100 orders counts as 100 responses/API credits.
Requests that return an empty array are billed as 0 responses/API credits and do not count against usage. Error responses are not charged.
Cursor pagination
Use the last row from the previous page and pass cursor as statusTimestamp_txIndex_oid. The oid suffix prevents rows with the same status timestamp and txIndex from being skipped across pages.
REST-style Example
curl -X POST "https://api-hyperliquid-index.n.dwellir.com/YOUR_API_KEY/info" \
-H "content-type: application/json" \
-d '{
"type": "historicalOrdersByTime",
"user": "0x1111111111111111111111111111111111111111",
"coin": "BTC",
"startTime": 1753606200000,
"endTime": 1753606300000,
"limit": 100
}'JSON-RPC Example
curl -X POST "https://api-hyperliquid-index.n.dwellir.com/YOUR_API_KEY/jsonrpc" \
-H "content-type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "historicalOrdersByTime",
"params": {
"user": "0x1111111111111111111111111111111111111111",
"coin": "BTC",
"startTime": 1753606200000,
"endTime": 1753606300000,
"limit": 100
}
}'Response
REST /info responses return an array directly. JSON-RPC responses return the same array under result. Empty matches return []; they are not errors.