Skip to main content
Player prop markets let you get odds on individual player performance — points scored, rebounds, assists, and more. TheRundown V2 API models player props as markets with type of TYPE_PLAYER.

Player Prop Market IDs

Individual Stats

Combo Markets

Combo markets combine two or three stats into a single over/under line.

Live / In-Play Variants

Live player props use separate market IDs but map to their prematch equivalents.

Discovering Available Prop Markets

The tables above are a reference, but not every sport or event will have every prop market. Use the market discovery endpoints to see which prop markets are currently available.

By sport and date

Returns all markets with active pricing for a sport on a given date. Filter to player props by checking the proposition field — prop markets have proposition: true.

By event ID

Returns only the markets available for a specific event. Useful when building a props view for a single game.
Pass the V2 event_id from the event payload into per-event endpoints. Do not substitute event_uuid. Use the discovered market IDs in the market_ids parameter when fetching events to get odds for those props.

Fetching Player Props

Request player prop markets by including the relevant market_ids in your events request.

Understanding Participants in Player Props

In player prop markets, participants represent the player (not the team). Each participant has: Within each participant, the lines array contains the over/under values and their prices from each sportsbook. Each line has a value field (a string, e.g., "25.5") and a prices map keyed by affiliate ID. Each price object includes the price, is_main_line boolean, and updated_at timestamp.
Join player props on participant.id, not name. For TYPE_PLAYER participants, id is the stable player ID — the same key used everywhere else in the API. Fetch the full player record (team, names, position) at GET /api/v2/players/{player_id}. Because each player has a distinct id, joining on id resolves shared-name collisions that joining on name cannot. To resolve a name to an id once, use the roster at GET /api/v2/teams/{team_id}/players. You can also narrow the response server-side with participant_ids (comma-separated, max 99) and participant_type=TYPE_PLAYER. See the Participant object reference for full definitions.

Example Response Structure

Fetching Combo Props

Combo markets combine multiple stats. The request pattern is the same — just use the combo market IDs.

Fetching All Props at Once

You can request all prop market IDs in a single call. This is useful if you want to build a comprehensive player props page.

Live Player Props

Live player props are available once a game starts. Use the live market IDs to fetch in-play prop odds.
You can also subscribe to live prop updates via the V2 Markets WebSocket:

Building a Player Props Display

Here is a complete example that organizes props by player for display in a UI.

Next Steps

Market IDs Reference

Full list of all market IDs

Getting Live Odds

Core game odds (moneyline, spread, total)

WebSocket Streaming

Real-time updates for live props

Historical Odds

Track prop line movement over time