Basketball Notes

Basketball-specific quirks — supported endpoints and the h2h sport_id requirement

Basketball is supported on V6 with a reduced endpoint surface. All other sports (football, tennis, cricket, baseball, hockey, …) follow the standard V6 schema documented elsewhere.

Supported Basketball Endpoints

Endpoint	Status
GET /api/v1/basketball/today	✅ Working
GET /api/v1/basketball/date?date=YYYY-MM-DD	✅ Working
GET /api/v1/basketball/future	✅ Working
GET /api/v1/match/{matchId}	✅ Working
GET /api/v1/match/{matchId}/odds	✅ Working
GET /api/v1/match/{matchId}/odds/{companyId}	✅ Working
GET /api/v1/h2h?home=...&away=...&sport_id=2	✅ Working — requires sport_id=2
GET /api/v1/match/{matchId}/stats	❌ Not available
GET /api/v1/match/{matchId}/team-stats	❌ Not available
GET /api/v1/match/{matchId}/lineups	❌ Not available
GET /api/v1/match/{matchId}/incidents	❌ Not available
GET /api/v1/match/{matchId}/commentary	❌ Not available
GET /api/v1/match/{matchId}/tables	❌ Not available

H2H Requires sport_id

The global /h2h endpoint defaults to football. For basketball you must explicitly pass sport_id=2:

New canonical

curl -H "x-api-key: YOUR_API_KEY" \
  "https://api.sportsapipro.com/v6/basketball/h2h?home={homeId}&away={awayId}&sport_id=2"

For richer basketball coverage (player stats, play-by-play, box scores) use the V2 Basketball API where supported, or the V4 Odds API for pre-match lines.