> ## Documentation Index > Fetch the complete documentation index at: https://docs.therundown.io/llms.txt > Use this file to discover all available pages before exploring further. # Get market participants > Lists teams, players, or result sides for the requested event and markets. Use `participant_id` from this response, rather than `id`, to filter a participant-specific chart. Market `3` totals use `TYPE_RESULT` Over and Under participants, while markets `1` and `2` use `TYPE_TEAM` participants. For example, discover totals with `GET /api/v2/markets/participants?event_id=733a06aa4f4f2a3af7872c3667a60f22&market_ids=3&participant_type=TYPE_RESULT`, then request each discovered side from `GET /api/v2/events/{eventID}/markets/{marketID}/history`. ## OpenAPI ````yaml get /api/v2/markets/participants openapi: 3.1.0 info: title: TheRundown Sports API version: 2.0.0 description: > **Resolve the event first.** Ambiguous date, team, player, or timezone? The agent asks instead of guessing. **Every price carries evidence.** Event, market, affiliate ID, line, and the price update time. A fetch time is not freshness. **Missing stays missing.** No remembered odds, no synthetic prices, no filled gaps. **IDs come from the API.** Sports, markets, and affiliates are discovered at runtime. Retired affiliates stay out. Real-time and historical sports betting data, odds, lines, and statistics across major North American and international sports leagues. ## Authentication All endpoints (except `/sports` and `/affiliates`) require authentication. Send your API key from a private server-side environment variable in the `X-TheRundown-Key` header. The query-key security scheme is retained for compatibility with existing integrations and deprecated for new integrations; do not put keys in URLs, prompts, browser bundles, or public code. ## Off-the-Board Sentinel Value The value **0.0001** indicates a line is "off the board" — the sportsbook has temporarily removed pricing (e.g., pending injury news). This is NOT an error. Display as "Off Board" or "N/A" in your UI. ## Rate Limiting Requests are rate-limited per API key tier. Check response headers for current limits. ## Data Updates - Live odds update in real-time during games - Use delta endpoints for efficient polling of changes - WebSocket connections available for streaming updates ## V1 vs V2 V2 endpoints use market-based data structures (market_id, participants, line prices). V1 endpoints use legacy line-based structures (moneyline, spread, total objects). V2 is recommended for new integrations. contact: name: TheRundown API Support url: https://therundown.io email: support@therundown.io termsOfService: https://therundown.io/terms servers: - url: https://therundown.io description: Production security: - ApiKeyHeader: [] tags: - name: V2 Sports description: Sport listings, dates, and teams (V2) - name: V2 Events description: Events with market-based odds (V2) - name: V2 Markets description: Market definitions, odds, deltas, and history (V2) - name: V2 Futures description: >- Futures/outright competition events — championship and tournament-winner boards (V2, early access) - name: V2 Teams description: Team data, players, and stats (V2) - name: V2 Players description: Player data (V2) - name: V2 Stats description: Team and player statistics (V2) - name: V2 WebSocket description: Real-time streaming via WebSocket (V2) - name: V2 Reference description: Reference data — affiliates, sportsbooks, season types (V2) - name: V1 Events description: Events with line-based odds (V1 legacy) - name: V1 Lines description: Moneyline, spread, total, best-line endpoints (V1 legacy) - name: V1 Sports description: Sport listings, dates, events, schedules (V1 legacy) - name: V1 Delta description: Delta/change feeds (V1 legacy) - name: V1 Reference description: Reference data (V1 legacy) - name: V1 WebSocket description: Real-time streaming via WebSocket (V1 legacy) externalDocs: description: Build with AI guide url: https://therundown.io/build-with-ai paths: /api/v2/markets/participants: get: tags: - V2 Markets summary: Get market participants description: >- Lists teams, players, or result sides for the requested event and markets. Use `participant_id` from this response, rather than `id`, to filter a participant-specific chart. Market `3` totals use `TYPE_RESULT` Over and Under participants, while markets `1` and `2` use `TYPE_TEAM` participants. For example, discover totals with `GET /api/v2/markets/participants?event_id=733a06aa4f4f2a3af7872c3667a60f22&market_ids=3&participant_type=TYPE_RESULT`, then request each discovered side from `GET /api/v2/events/{eventID}/markets/{marketID}/history`. operationId: v2GetMarketsParticipants parameters: - name: market_ids in: query schema: type: string default: 1,2,3 example: '3' description: Comma-separated market IDs. Defaults to `1,2,3` when omitted. - name: event_id in: query required: true schema: type: string example: 733a06aa4f4f2a3af7872c3667a60f22 description: Canonical V2 event ID that scopes participant discovery. - name: participant_ids in: query schema: type: string description: Comma-separated public canonical participant IDs to return. - name: participant_type in: query schema: type: string enum: - TYPE_TEAM - TYPE_PLAYER - TYPE_RESULT example: TYPE_RESULT description: Filter by participant type. responses: '200': description: Market participants content: application/json: schema: $ref: '#/components/schemas/MarketParticipantsResponse' example: participants: - id: 70001 market_event_id: 28401 participant_id: 9 participant_type: TYPE_RESULT participant_name: Over updated_at: '2026-09-09T19:00:00Z' - id: 70002 market_event_id: 28401 participant_id: 10 participant_type: TYPE_RESULT participant_name: Under updated_at: '2026-09-09T19:00:00Z' components: schemas: MarketParticipantsResponse: type: object properties: participants: type: array items: $ref: '#/components/schemas/MarketParticipant' MarketParticipant: type: object properties: id: type: integer format: int64 market_event_id: type: integer format: int64 participant_id: type: integer participant_type: type: string enum: - TYPE_TEAM - TYPE_PLAYER - TYPE_RESULT participant_name: type: string updated_at: type: string format: date-time securitySchemes: ApiKeyHeader: type: apiKey in: header name: X-TheRundown-Key description: Recommended API key request header for new integrations ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.