Get Orders
Trading
Get Orders
Retrieve open orders for the authenticated user
GET
Get Orders
Overview
The Get Orders endpoint returns a paginated list of the user’s open orders across all markets or filtered by specific criteria. This includes active limit orders and partially filled orders.Authentication
This endpoint requires CLOB authentication with HMAC signature verification. Required Headers:KUEST_ADDRESS- User’s wallet addressKUEST_API_KEY- API key from trading auth credentialsKUEST_PASSPHRASE- Passphrase from trading auth credentialsKUEST_TIMESTAMP- Current Unix timestamp (seconds)KUEST_SIGNATURE- HMAC signature of the requestAccept: application/json
Query Parameters
Filter orders by maker address (typically the proxy wallet address)
Filter to a specific order ID
Filter orders by market condition ID
Filter orders by outcome token ID
Pagination cursor from previous response (base64 encoded)
Response
Array of open order objects
Unique order identifier
Order status:
live, partially_filled, pendingMarket condition ID
Original order size in decimal format
Outcome identifier (optional)
Maker’s address (proxy wallet)
Owner API key
Order price (decimal between 0 and 1)
Order side:
BUY or SELLAmount already filled (decimal format)
Outcome token ID
Expiration timestamp in seconds (“0” for no expiration)
Order type:
GTC, GTD, FOK, FAKISO 8601 timestamp when order was created
ISO 8601 timestamp when order was last updated
Pagination cursor for next page. Returns
LTE= when no more results.Normalized Order Response
The API wrapper normalizes CLOB orders into a user-friendly format:Order ID
buy or sell (lowercase)Order type:
GTC, GTD, FOK, FAKOrder status (e.g.,
live)Order price between 0 and 1
Maker amount in micro units
Taker amount in micro units
Filled amount in micro units
ISO 8601 creation timestamp
Unix timestamp or null if no expiration
Market metadata
Market condition ID
Market title
Market URL slug
Whether market is active
Whether market is resolved
Market icon URL (optional)
Parent event slug (optional)
Parent event title (optional)
Pagination
The endpoint uses cursor-based pagination:- First request returns orders and
next_cursor - Include
next_cursorin subsequent requests - When
next_cursorisLTE=, no more results exist - Each page returns up to 100 orders