Today's Orders
Paginated active orders for an account from the trade read service: open orders plus today’s terminal activity. Default source is the v2 cache; optional PostgreSQL reads use the same domain order shape as WebSocket updates.
Use Case: Drive a live blotter or reconcile REST snapshots with accUpdates by merging on clOrdId.
Compared to v1 account orders
Account Orders (GET /v2/accounts/{id}/orders) returns legacy field names (orderType, status, quantity, …) and an availability object. This v2 endpoint returns domains/order.Order objects (field names type, ordStatus, qty, …) and paginates with nextCursor instead of bundling availability metadata.
Response envelope
Every 200 response includesorders (array, never null — may be empty) and nextCursor (int64, 0 when there are no more pages). Each order always includes clOrdId, accountId, symbol, quantity/price fields (qty, price, stopPrice, cumQty, leavesQty, avgPrice), and createdAt / updatedAt. Fields such as side, type, ordStatus, and legs may be omitted when unset.
Demo response (v2 shape)
Numeric quantities and prices are returned as decimal strings to preserve precision. The shape is consistent whether the data was served from cache or the database.Authorizations
OAuth2 Bearer token: obtain an access token from the token endpoint and send it in the Authorization header.
Path Parameters
Account ID whose active orders you want to read. Use the account identifier from the user's account list or trading setup.
Query Parameters
Where to read orders from. Use cache for live screens and order tickets. Use db when you need the stored database view. Keep the same source while paginating.
cache, db Maximum number of orders to return in this page. Use smaller values for UI lists and larger values for back-office exports. Default is 50; maximum is 500.
1 <= x <= 500Opaque pagination cursor. Send 0 (or omit) for the first page; pass the previous response's nextCursor for subsequent pages. Stop when nextCursor is 0.
Response
Page of active orders
Paginated v2 orders response from GET /v2/accounts/{id}/orders and GET /v2/accounts/{id}/orders/history. Both fields are always present; orders may be an empty array when there are no matches.