NBA Odds API Guide

Описание: In this video, we show you how to pull data and NBA odds from our Odds API.

If you are building a basketball or multi-sport betting application, the core of our system for fetching NBA odds—including moneylines, spreads, totals, player props, and alt-lines—is accessed through a single unified endpoint: /v2/events.

Step 1: Making the Basic Odds API Request
To get started, the easiest way to fetch events along with their standard game odds and player props is by querying that /v2/events endpoint. You primarily use three key parameters:
1. leagueID=NBA: This restricts the results to only NBA events.
2. oddsAvailable=true: This ensures that we only return events where betting odds are currently open.
3. limit=10: This sets a maximum number of events to return, though you can increase this if needed. We generally recommend keeping the limit reasonable to maintain speed.
When you use this basic pattern, the API returns NBA games with standard markets (moneyline, spread, totals) plus any available player props for those games. A useful note about usage: 1 object equals 1 event, regardless of how many odds (which could be hundreds) are returned across those events, meaning you are only charged once per event.

Step 2: Getting Specific Prop Markets
Where the API becomes powerful is in filtering the results. If you want to get more fine-grained and focus on specific bet types, you use the oddIDs parameter.
For example, if you wanted to pull the full-game points over/unders for all players where that market is available, you would use this specific comma-separated list in the oddIDs parameter:
• points-PLAYER_ID-game-ou-over
• points-PLAYER_ID-game-ou-under
The PLAYER_ID value here is special; it means "any player ID". You can mix and match any available market patterns in a comma-separated list via oddIDs to pull exactly the markets you care about, such as points, assists, rebounds, or made threes.

Step 3: Targeting Individual Players
If you want odds for a specific player, you simply swap the general PLAYER_ID value with a specific player's ID in the oddIDs pattern.
Conceptually, every single bet is defined by an oddID that follows this structural format:
{statID}-{statEntityID}-{periodID}-{betTypeID}-{sideID}
For instance, the oddID points-JALEN\_DUREN\_1\_NBA-game-ou-over breaks down like this:
• points: The stat (player points).
• JALEN\_DUREN\_1\_NBA: The statEntityID (the specific player’s ID in our system).
• game: The period (full game).
• ou: The bet type (over/under).
• over: The side (the over side of the market).

Step 4: Optimizing Your Queries
To keep responses fast and ensure the data payload is small, we strongly recommend several optional parameters:
• Trimming oddIDs: Only include the markets you actually need.
• Specifying bookmakerID: Use this to include odds only from the books you care about, such as bookmakerID=fanduel,draftkings,caesars,betmgm.
• includeOpposingOdds=true: When this is set, you only need to list the over side in your oddIDs, and we automatically include the corresponding under odds in the response.
• includeAltLines=true: This adds alternate lines (like multiple point totals for the same player). While powerful, you should use it only when necessary, as it can slow response times and increase response size.
Once you are comfortable using the leagueID, oddIDs, and key parameters like bookmakerID, you can shape the NBA feed to perfectly match almost any modeling or betting use case—without ever wasting objects on unwanted markets.

Sign up to our Odds API here: https://sportsgameodds.com/pricing/