> ## Documentation Index > Fetch the complete documentation index at: https://docs.limitless.exchange/llms.txt > Use this file to discover all available pages before exploring further. # Get User Orders > Returns a bare, newest-first array of the effective profile's orders for one exact market slug. Omitted statuses default to LIVE. Partner HMAC tokens with `delegated_signing` may select an owned sub-account with `x-on-behalf-of`. Returns a bare JSON array of orders for the effective profile and one exact market slug. Group slugs and stable-slug aliases are not accepted. Results are ordered newest first. ## Authentication and delegation Use HMAC authentication. Looking up your own orders does not require a specific token scope. To read a managed sub-account, send `x-on-behalf-of: `. The HMAC token must carry `delegated_signing`, and the target profile must belong to the authenticated partner. ### Status filters If `statuses` is omitted, the API returns live orders. Supported status filters are `LIVE`, `MATCHED`, `CANCELED`, and `UNMATCHED`. Repeat the query parameter to request multiple statuses. Values are case-insensitive. A taker rejected by self-trade prevention terminates as `CANCELED` (the placement response carries `execution.reason: "STP_TAKER_REJECTED"`); filter for it with `CANCELED`. ## Limit and response When supplied, `limit` must be an integer from 1 through 200. If omitted, the result is unbounded. The endpoint has no cursor, page, total, or other pagination metadata. The response is the array itself, not an `{ "orders": [...] }` envelope. Each item contains the internal order and owner/market/token identifiers, order type, status, side, maker and taker amounts, price, original and remaining size, and creation time. Numeric values are serialized as decimal strings. `clientOrderId` is present only when the order was placed with one. An existing market with no matching orders returns `[]`. ## Errors | Status | Meaning | | ------ | ---------------------------------------------------------------------------------------------- | | `400` | A path/query value or the delegated header is invalid, or an unknown query field was supplied. | | `401` | Authentication failed. | | `403` | Delegation lacks `delegated_signing` or the target is not owned by the partner. | | `404` | The exact market slug or effective profile was not found. | | `500` | The user-order lookup failed unexpectedly. | ## OpenAPI ````yaml GET /markets/{slug}/user-orders openapi: 3.0.0 info: title: Limitless Exchange API description: >- # Limitless Exchange Trading API *Production-ready API for prediction market trading, portfolio management, and market data* > 🎯 **Quick Navigation**: [Authentication](#tag/authentication) | [Markets](#tag/markets) | [Trading](#tag/trading) | [Portfolio](#tag/portfolio) --- ## 🚀 Quick Start Choose your preferred programming language for complete end-to-end implementation: ### Overview The Limitless Exchange API offers both REST and WebSocket integration: **REST API (Trading)**: 1. **🔐 Authentication**: Use API key for all programmatic access 2. **📊 Fetch Market Data**: Get market info including venue contract addresses (once per market) 3. **📋 Order Creation**: Build and sign orders using EIP-712 structured data 4. **🚀 Order Submission**: Submit signed orders and receive confirmations **WebSocket API (Real-Time Data)**: 1. **🔌 Connection**: Connect to `/markets` namespace for real-time updates 2. **📊 Subscriptions**: Subscribe to market prices and position changes 3. **📡 Events**: Handle live market data and transaction updates ### 🔐 Authentication for API Users > **⚠️ DEPRECATION NOTICE**: Cookie-based session authentication is deprecated and will be removed within weeks. Please migrate to API keys immediately. | Method | Header | Status | |--------|--------|--------| | **API Key** | `X-API-Key: lmts_...` | ✅ Required for programmatic access | | Cookie Session | `Cookie: limitless_session=...` | ⚠️ Deprecated (removal imminent) | **Getting an API Key** API keys can only be created via the Limitless Exchange UI: 1. Log in to [limitless.exchange](https://limitless.exchange) using your wallet 2. Click your profile menu (top right) 3. Select "Api keys" 4. Generate a new key **Using Your API Key** Include in all requests via the `X-API-Key` header: ```bash # REST API curl -H "X-API-Key: lmts_your_key_here" https://api.limitless.exchange/markets # WebSocket - pass X-API-Key header during connection handshake ``` ### Migration from Cookie to API Key If you're currently using cookie-based authentication, migrate by: 1. **Generate an API key** via the UI (profile menu → Api keys) 2. **Replace cookie header** with API key header: ```diff # Before (deprecated) - Cookie: limitless_session=your_session_token # After + X-API-Key: lmts_your_key_here ``` 3. **Remove session management code** - no more login flow or cookie handling needed ### Important: Venue System for CLOB Markets CLOB markets use a **venue system** where each market is associated with specific contract addresses. Before placing orders: 1. **Fetch market data once**: `GET /markets/:slug` returns venue information 2. **Use venue.exchange**: This is the `verifyingContract` for EIP-712 order signing 3. **Cache the venue**: Venue data is static per market - fetch once and reuse **Sample venue response:** ```json { "venue": { "exchange": "0xA1b2C3...", "adapter": "0xD4e5F6..." } } ``` ### Required Approvals Before trading, set up token approvals based on order type: | Order Type | Market Type | Approve To | |------------|-------------|------------| | BUY | All CLOB | USDC → `venue.exchange` | | SELL | Simple CLOB | CT → `venue.exchange` | | SELL | NegRisk/Grouped | CT → `venue.exchange` AND `venue.adapter` | ### Checksummed Addresses All addresses must use **checksummed format** (EIP-55 mixed-case): - Authentication: `x-account` header - Orders: `maker` and `signer` fields - Example: `0x5aAeb6053F3E94C9b9A09f33669435E7Ef1BeAed` ### Implementation Guides **[🐍 Python Quick Start](#description/-python-quick-start)** - REST API: eth-account, requests, and web3.py libraries - WebSocket: python-socketio, asyncio integration **[☕ Java Quick Start](#description/-java-quick-start)** - REST API: Web3j, OkHttp3, and Jackson libraries **[📦 Node.js/TypeScript Quick Start](#description/-nodejs-typescript-quick-start)** - REST API: viem, ethers, and cross-fetch libraries - WebSocket: socket.io-client for real-time trading - Full TypeScript support with end-to-end examples **[🔌 WebSocket Integration](#description/-websocket-integration)** - Real-time market data and position updates - Production-ready Python client with authentication --- ## 🐍 Python Quick Start Complete end-to-end Python implementation for Limitless Exchange API integration. ### 🐍 Python E2E Order Creation Guide Complete Python implementation guide is being loaded from external documentation... **Guide Contents:** - 🔐 Complete authentication flow with eth-account - 📋 Order construction with Web3.py calculations - ✍️ EIP-712 structured data signing - 🚀 Order submission with requests library - ⚠️ Comprehensive error handling - 🛠️ Production deployment considerations *For the complete Python guide, ensure the file is available at docs/scripts-samples/python-e2e-order-creation.md* ## ☕ Java Quick Start Complete end-to-end Java implementation for Limitless Exchange API integration. ### ☕ Java E2E Order Creation Guide Complete Java enterprise implementation guide is being loaded from external documentation... **Guide Contents:** - 🔐 Complete authentication flow with Web3j - 📋 Order construction with BigInteger precision - ✍️ EIP-712 structured data signing - 🚀 Order submission with OkHttp3 - ⚠️ Enterprise error handling patterns - 🏗️ Production Maven project structure *For the complete Java guide, ensure the file is available at docs/scripts-samples/java-e2e-order-creation.md* ## 📦 Node.js/TypeScript Quick Start Complete end-to-end Node.js/TypeScript implementation for trading and WebSocket subscriptions. ### 📦 Node.js/TypeScript Trading & WebSocket Guide Complete Node.js/TypeScript implementation guide is being loaded from external documentation... **Guide Contents:** - 🔐 **Authentication**: Wallet-based auth with ethers and viem - 📋 **Order Creation**: EIP-712 signing with viem WalletClient - 🚀 **Order Submission**: REST API integration with cross-fetch - 🔌 **WebSocket Subscriptions**: socket.io-client for real-time updates - 📊 **Market Data**: AMM prices and CLOB orderbook subscriptions - ⚠️ **Type Safety**: Full TypeScript support with proper types - 🛠️ **Production Ready**: Complete end-to-end working example **Key Features:** - **Combined Subscriptions**: Subscribe to both AMM and CLOB markets simultaneously - **Authentication Flow**: Complete wallet-based authentication with session management - **Trading Integration**: Place orders and receive real-time updates - **TypeScript First**: Type-safe implementation with proper interfaces *For the complete Node.js guide, ensure the file is available at docs/scripts-samples/node-socket-trading-and-subscribe.md* ## 🔌 WebSocket Integration Real-time market data and position updates using WebSocket connections. ### 🔌 WebSocket Real-Time Integration Guide Complete WebSocket implementation guide is being loaded from external documentation... **Guide Contents:** - 🔌 **WebSocket Connection**: python-socketio client with async support - 🔐 **Authentication**: JWT session cookie integration - 📊 **Market Subscriptions**: Real-time price updates and position changes - ⚡ **Event Handling**: Comprehensive event processing patterns - 🔄 **Auto-Reconnection**: Production-ready reconnection logic - 🛠️ **Error Recovery**: Robust error handling and fallback strategies **Key Features:** - **Public Mode**: Market price updates without authentication - **Authenticated Mode**: Full access to positions and transactions - **Multi-Market Support**: Subscribe to multiple markets simultaneously - **Production Ready**: Tested patterns for production deployment *For the complete WebSocket guide, ensure the file is available at docs/scripts-samples/python-socket-subscribe.md* version: '1.0' contact: name: API Support url: https://limitless.exchange email: hey@limitless.network servers: - url: https://api.limitless.exchange description: Production API security: [] tags: - name: Authentication description: User authentication and session management - name: Markets description: Browse, search, and analyze prediction markets - name: Market Navigation description: Navigation tree, market pages, and property filters - name: Trading description: Create, manage, and cancel orders - name: Portfolio description: Position tracking, trade history, and performance - name: Feed description: Public trading activity feeds paths: /markets/{slug}/user-orders: get: tags: - Trading summary: User Orders description: >- Returns a bare, newest-first array of the effective profile's orders for one exact market slug. Omitted statuses default to LIVE. Partner HMAC tokens with `delegated_signing` may select an owned sub-account with `x-on-behalf-of`. operationId: MarketOrderbookController_getUserOrders parameters: - name: statuses required: false in: query description: >- Repeat to filter by one or more statuses. Values are case-insensitive and normalized to uppercase. Defaults to LIVE when omitted. style: form explode: true schema: type: array items: type: string enum: - LIVE - MATCHED - CANCELED - UNMATCHED - name: limit required: false in: query description: Maximum newest orders to return. Must be 1–200 when supplied. schema: type: integer minimum: 1 maximum: 200 example: 100 - name: slug required: true in: path description: >- Exact market slug. Group slugs and stable-slug aliases are not resolved. schema: type: string example: presidential-election-2024 - name: x-on-behalf-of in: header description: >- Managed sub-account profile ID. Requires an HMAC token with `delegated_signing` and a partner relationship with the target. required: false schema: type: integer minimum: 1 maximum: 2147483647 example: 326 responses: '200': description: >- Bare newest-first array; an existing market with no matching orders returns `[]` content: application/json: schema: type: array items: $ref: '#/components/schemas/UserOrder' '400': description: >- Invalid slug/query parameter, unknown query field, or malformed delegation header content: application/json: schema: oneOf: - $ref: '#/components/schemas/ValidationErrorResponse' - $ref: '#/components/schemas/NestErrorResponse' '401': description: Authentication failed content: application/json: schema: $ref: '#/components/schemas/NestErrorResponse' '403': description: >- Delegation lacks `delegated_signing` or the target is not owned by the partner content: application/json: schema: $ref: '#/components/schemas/NestErrorResponse' '404': description: Exact market slug or effective profile was not found content: application/json: schema: $ref: '#/components/schemas/ErrorMessageResponse' '500': description: User-order lookup failed unexpectedly content: application/json: schema: $ref: '#/components/schemas/ErrorMessageResponse' security: - HmacAuth: [] components: schemas: UserOrder: type: object properties: id: type: string format: uuid description: Internal order ID. ownerId: type: integer description: Profile that owns the order. marketId: type: string description: Internal market ID serialized as text. token: type: string description: Conditional position token ID. type: type: string enum: - GTC - FAK - FOK status: type: string enum: - LIVE - MATCHED - CANCELED - UNMATCHED side: type: string enum: - BUY - SELL makerAmount: type: string pattern: ^[0-9]+(?:\.[0-9]+)?$ description: Maker amount in raw 6-decimal units, serialized as a decimal string. takerAmount: type: string pattern: ^[0-9]+(?:\.[0-9]+)?$ description: Taker amount in raw 6-decimal units, serialized as a decimal string. price: type: string pattern: ^[0-9]+(?:\.[0-9]+)?$ description: Order price serialized as a decimal string. example: '0.5' originalSize: type: string pattern: ^[0-9]+(?:\.[0-9]+)?$ description: >- Original contract size in raw 6-decimal units, serialized as a decimal string. remainingSize: type: string pattern: ^[0-9]+(?:\.[0-9]+)?$ description: >- Unfilled contract size in raw 6-decimal units, serialized as a decimal string. createdAt: type: string format: date-time clientOrderId: type: string description: Caller-assigned identifier when the order was placed with one. additionalProperties: false description: >- Order returned by the market user-orders read. Numeric values are serialized as decimal strings. required: - id - ownerId - marketId - token - type - status - side - makerAmount - takerAmount - price - originalSize - remainingSize - createdAt ValidationErrorResponse: type: object properties: message: type: array items: $ref: '#/components/schemas/ValidationErrorItem' error: type: string enum: - Bad Request statusCode: type: number enum: - 400 additionalProperties: false required: - message - error - statusCode NestErrorResponse: type: object properties: message: type: string error: type: string statusCode: type: integer additionalProperties: false required: - message - error - statusCode ErrorMessageResponse: type: object properties: message: type: string additionalProperties: false required: - message ValidationErrorItem: type: object properties: field: type: string example: orderIds message: type: string example: orderIds should not be empty additionalProperties: false required: - field - message securitySchemes: HmacAuth: type: apiKey in: header name: lmts-api-key description: >- Scoped API token with HMAC-SHA256 signing. Requires three headers: lmts-api-key (token ID), lmts-timestamp (ISO-8601), lmts-signature (Base64-encoded HMAC). See Authentication docs for details. ````