Answer

Player Props API: Sportsbook Odds and Examples

Fetch player prop odds by sport, bookmaker and market. Start with an NFL touchdown request, inspect the response, and test your coverage before choosing a plan.

How do I get player prop odds through an API?

Use ParlayAPI's /v1/sports/{sport_key}/props endpoint to fetch player lines and available Over/Under prices, filtered by bookmaker, market, player or event. Start with one bookmaker and one market. Availability varies by sport, event and time; a listed integration is not a promise of a complete board.

Try it with your own key

Get a free key, run the request below, then choose an allowance for the queries and refresh schedule you actually need.

Get a free API key Set up your first request Compare current plans

Start with the market your project needs

For an NFL touchdown model, the example below requests DraftKings player_anytime_td. That market represents at least one scored touchdown at line 0.5. Passing touchdowns and higher touchdown thresholds are different markets. A successful request can return an empty list when no matching rows are available.

The default response is a JSON list with a player display name, market_key, line, bookmaker, over_price and under_price. With grouped=true, bookmaker-specific values move into books[]. A missing price is not the opposite side of a two-way quote. Player names can differ between books; there is no universal cross-book athlete ID in this response.

Build your comparison around the same event, player, market, period and line. For DFS pick'em apps, use the separate DFS guide: a projection or payout multiplier is not interchangeable with a sportsbook price.

Endpoint

GET /v1/sports/{sport_key}/props

curl -i 'https://parlay-api.com/v1/sports/americanfootball_nfl/props?bookmakers=draftkings&markets=player_anytime_td&limit=25&offset=0' \
  -H 'X-API-Key: YOUR_KEY'

Replace YOUR_KEY with your dashboard key. The -i option prints HTTP status and headers as well as the body. This is a request template, not a captured live result; your account's request credits apply.

What to check in the response

Status first: handle an error response before interpreting the body as a list of props.
Pagination: follow x-next-offset while x-result-has-more is true. Limit and offset count rows even with grouped=true.
Completeness: inspect x-result-truncated and x-result-degraded. The last page of a limited board does not establish full sportsbook coverage.
Freshness: inspect each source's timestamps and age_seconds. Separate pages are not a frozen snapshot and can change between requests.

FAQ

Can I test player props before choosing a paid plan?

Create a free API key, run a narrow REST request, and check the returned markets, sources and credit use. The Free plan has 1,000 credits per month. Current paid allowances and billing options are on the pricing page; test your required coverage before choosing one.

How do I request FanDuel or another bookmaker?

Change the bookmakers filter to the required key, such as fanduel, and keep the same market and sport. Compare each response and its completeness headers. A bookmaker's catalog entry does not guarantee that a particular player or market is available.

Does a player props API include historical snapshots?

Current props and historical closing lines are separate endpoints with different coverage. Verify the exact sport, bookmaker, market and dates in the historical coverage guide. A closing line is not a complete intraday price history.

Player props reference DFS lines and payout multipliers How to evaluate a props API NBA player props Historical coverage