TypeScript SDK — Trading: History & Volume
Methods for querying active orders, historical orders, past trades, and trading-volume statistics. All methods are on client.trading.
Every method in this namespace is a POST mutation — the SDK will not automatically retry on failure.
See the API Specifications for full request/response schemas.
listActiveOrders
POST /v1/orders · Authenticated
Retrieve all currently active (live) orders on the account.
Code
Tip: For real-time order updates without polling, subscribe to
client.websocket.orders()instead. See the WebSocket Reference.
listPastOrders
POST /v1/orders/history · Authenticated
Retrieve historical orders. You can filter by timestamp to paginate through results.
Code
Caveat: The
timestampfield is a millisecond epoch value and may bebigint. The SDK accepts bothbigintandnumberfor int64 input fields.
listPastTrades
POST /v1/mytrades · Authenticated
Retrieve your executed trades (fills). Each entry represents one side of a matched trade.
Code
Caveat: The
tid(trade ID) field in the response is abigint. Thetimestampinput accepts bothbigintandnumber.
Tip: Prices, amounts, and fees are decimal strings. See Data Types.
getTradingVolume
POST /v1/tradevolume · Authenticated
Retrieve your 30-day trading volume, broken down by fee tier and trading pair.
Code
Tip: Volume values are decimal strings. Count values (
buy_maker_count, etc.) are numbers.
getNotionalTradingVolume
POST /v1/notionalvolume · Authenticated
Retrieve your 30-day notional trading volume in USD. This is used to determine your fee tier.
Code
Tip: The
notional_30d_volumefield is a decimal string, whileapi_maker_fee_bpsandapi_taker_fee_bpsare numbers (basis points).
What's next
- Trading: Order Lifecycle — place, cancel, and inspect orders
- WebSocket Reference — real-time order and trade streams
- Patterns — pagination and common workflows
- Data Types — decimal strings and bigint handling