> ## 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 Pack Positions (Public) > Returns a profile's public pack (parlay) positions by Ethereum address, newest first. Only ACTIVE, WON, and LOST positions are included. Returns a user's pack (parlay) positions by Ethereum address, newest first. Public, no authentication required. The response includes only `ACTIVE`, `WON`, and `LOST` positions; internal lifecycle states never appear here. ## When to use Use this endpoint to render a packs positions list on a public profile view. Pass any wallet address; you do not need to be that user. For your own positions with private fields (wallet, transaction hashes, vig), use the authenticated positions endpoint instead. ## Response contract The `200` body is a paginated page: `data`, `limit`, `page`, `totalPages`, and `totalRows`. * Each position carries its status, stake, multiplier, claim state (`isClaimed`), leg details, and the source pack it was bought from (`null` for custom packs). * The public payload deliberately excludes wallet addresses, token IDs, transaction hashes, and vig fields. * The API sorts positions by creation time, newest first. ## Filtering and pagination * `status` narrows the list to a single status: `ACTIVE`, `WON`, or `LOST`. Any other value returns `400 Bad Request`. Omit it to return all three. * The API clamps `limit` server-side to the range 1-50. The default is 20. * `offset` defaults to 0. The API caps it at 10,000; a larger offset returns `400 Bad Request`. * `totalRows` always reflects the full matching count, while `totalPages` stops at the last browsable page under the offset cap. ## Address handling The `account` path parameter accepts a checksummed (EIP-55) or lowercase Ethereum address. A malformed address returns `400 Bad Request`. An address with no profile returns `404 Not Found`. ## Caching Responses carry `Cache-Control: public, max-age=5, s-maxage=15`, so CDN edges may serve a cached copy for up to 15 seconds. Status and claim state can trail the live database by roughly 30 seconds in the worst case. The authenticated owner endpoint is uncached. ## OpenAPI ````yaml GET /parlay/{account}/positions 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: /parlay/{account}/positions: get: tags: - Public Portfolio summary: Get public pack positions by account description: >- Returns a profile's public pack (parlay) positions by Ethereum address, newest first. Only ACTIVE, WON, and LOST positions are included. operationId: ParlayController_getPublicParlays parameters: - name: account required: true in: path description: User Ethereum address schema: example: '0x742d35Cc6634C0532925a3b844Bc454e4438f44e' type: string - name: limit required: false in: query description: Page size. Clamped server-side to the range 1-50. schema: type: number default: 20 minimum: 1 maximum: 50 - name: offset required: false in: query description: Number of positions to skip. Offsets above 10000 return 400. schema: type: number default: 0 minimum: 0 maximum: 10000 - name: status required: false in: query description: Filter to a single status. Omit to return all public statuses. schema: type: string enum: - ACTIVE - WON - LOST responses: '200': description: Paginated public pack positions, newest first content: application/json: schema: $ref: '#/components/schemas/PublicParlayPositionsPageDto' '400': description: Invalid Ethereum address, unsupported status, or offset above 10000 '404': description: Profile not found, or packs are disabled platform-wide components: schemas: PublicParlayPositionsPageDto: type: object properties: data: type: array items: $ref: '#/components/schemas/PublicParlayResponseDto' limit: type: number description: Effective page size (capped server-side) page: type: number description: 1-based page index derived from `offset/limit` totalPages: type: number description: Capped at the last browsable page (offset 10000) totalRows: type: number description: Full matching count, not capped required: - data - limit - page - totalPages - totalRows PublicParlayResponseDto: type: object properties: id: type: string status: type: string enum: - ACTIVE - WON - LOST stakeAmount: type: string description: USDC stake, in raw token units collateralDeposited: type: string multiplierOffered: type: string isClaimed: type: boolean description: True once the winnings claim transaction has been recorded resolvedAt: type: string format: date-time nullable: true createdAt: type: string legs: type: array items: $ref: '#/components/schemas/ParlayLegResponseDto' sourcePack: nullable: true description: >- The curated pack this position was bought from (null for custom packs) allOf: - $ref: '#/components/schemas/ParlaySourcePackDto' required: - id - status - stakeAmount - collateralDeposited - multiplierOffered - isClaimed - createdAt - legs ParlayLegResponseDto: type: object properties: id: type: string legIndex: type: number marketId: type: number marketSlug: type: string marketTitle: type: string marketImageUrl: type: string nullable: true description: Logo/crest image URL from the leg market group: nullable: true description: Group context for this leg (null for non-grouped markets) allOf: - $ref: '#/components/schemas/ParlayLegGroupDto' leagueName: type: string nullable: true description: >- Solo market's own league. Set for solo market legs only; grouped legs use `group.leagueName`. startMatchTimestamp: type: number nullable: true description: Solo market kickoff time (epoch seconds); null when not scheduled conditionId: type: string outcome: type: string enum: - 'YES' - 'NO' priceAtCreation: type: string resolutionStatus: type: string enum: - LOST - PENDING - WON resolvedAt: type: string format: date-time nullable: true esportsPropType: type: string enum: - map_handicap - map_winner - total_maps nullable: true description: >- Which typed esports prop this leg is, so it can be drawn as a prop of a fixture rather than as the fixture. Null on match winners and on every non-esports market. outcomeLabels: type: array nullable: true minItems: 2 maxItems: 2 items: type: string description: >- For named-outcome markets: labels as [homeTeam/YES, awayTeam/NO]. Null when labels are unavailable. outcomeImageUrls: type: array nullable: true minItems: 2 maxItems: 2 items: type: string nullable: true description: >- Outcome-specific artwork as [homeTeam/YES, awayTeam/NO]. Null when no artwork is available. required: - id - legIndex - marketId - conditionId - outcome - priceAtCreation - resolutionStatus ParlaySourcePackDto: type: object properties: id: type: string name: type: string required: - id - name ParlayLegGroupDto: type: object properties: id: type: number slug: type: string title: type: string leagueName: type: string nullable: true description: Match group's league/discipline homeTeam: type: string nullable: true awayTeam: type: string nullable: true homeScore: type: number nullable: true awayScore: type: number nullable: true startMatchTimestamp: type: number nullable: true description: Match kickoff time (epoch seconds); null for non-sports groups required: - id - slug - title ````