Schedules, standings, teams, players, and games
Used throughout PlayerWON for schedules, standings, boxscores, team pages, player pages, goalie pages, and model features.
PlayerWON combines publicly available NHL data with sportsbook odds data to power schedules, statistics, matchup pages, model predictions, and betting tools.
Used throughout PlayerWON for schedules, standings, boxscores, team pages, player pages, goalie pages, and model features.
Used for price comparisons, implied probability, fair odds, edge calculations, expected value, and odds history.
Predictions are generated from our own processing, feature engineering, and machine-learning models built on the source data below.
PlayerWON does more than display API responses. The source data is collected, stored, cleaned, combined, and transformed before it appears on the site.
Retrieve publicly available NHL data and licensed market odds data from external APIs.
Save raw and processed records in PlayerWON’s own database for fast access and historical tracking.
Clean, combine, validate, and structure the data into site-ready tables and model features.
Present the processed results as schedules, standings, predictions, statistics, matchup pages, and betting tools.
These endpoints support the NHL schedules, standings, teams, players, goalies, boxscores, and historical analysis shown across PlayerWON.
Used to identify available seasons, season boundaries, and season-based logic.
https://api-web.nhle.com/v1/standings-season
Open endpoint
Used for up-to-date team positions, division rankings, conference standings, and playoff-race context.
https://api-web.nhle.com/v1/standings/now
Open endpoint
Used to retrieve standings from specific dates for historical comparisons and season snapshots.
https://api-web.nhle.com/v1/standings/YYYY-MM-DD
Open sample request
Used to retrieve NHL schedules, matchup details, start times, participating teams, and game identifiers.
https://api-web.nhle.com/v1/schedule/YYYY-MM-DD
Open sample request
Used for final scores, shot totals, skater statistics, goalie summaries, and game-detail pages.
https://api-web.nhle.com/v1/gamecenter/{gameId}/boxscore
Open sample request
Provides player details such as position, handedness, height, weight, birthplace, current team, and career context.
https://api-web.nhle.com/v1/player/{playerId}/landing
Open sample request
Used to identify NHL teams and retrieve official IDs, names, and abbreviations.
https://api.nhle.com/stats/rest/en/team
Open endpoint
Used for season-level team statistics, historical comparisons, standings context, and model feature generation.
https://api.nhle.com/stats/rest/en/team/summary?cayenneExp=seasonId={seasonId} and gameTypeId=2
Open sample request
PlayerWON uses sportsbook data to compare market prices against model probabilities and support fair-odds, implied-probability, edge, and expected-value tools.
PlayerWON does not operate a sportsbook or accept wagers. Odds data is used for analytics, market comparison, and educational tools.
Used to identify supported sports and their API keys before querying market data.
https://api.the-odds-api.com/v4/sports/?apiKey=YOUR_API_KEY
View documentation
Used to retrieve upcoming event prices from sportsbooks for supported markets such as moneyline, spreads, and totals.
https://api.the-odds-api.com/v4/sports/{sport}/odds?regions=us&markets=h2h&oddsFormat=american&apiKey=YOUR_API_KEY
View documentation
Used for backtesting, model evaluation, price-history analysis, and comparison against pre-game market conditions.
https://api.the-odds-api.com/v4/historical/sports/{sport}/odds?regions=us&markets=h2h&date=YYYY-MM-DDTHH:MM:SSZ&apiKey=YOUR_API_KEY
View historical odds documentation
Used to determine which market types are available, including head-to-head, spreads, and totals.
Examples: h2h, spreads, totals
View supported markets
Data displayed on PlayerWON is retrieved from third-party public or licensed API sources and then processed into PlayerWON’s own database, views, calculations, and model outputs.
Although data pipelines are updated regularly, source data may occasionally contain delays, inconsistencies, omissions, or live-update issues.
Questions or possible data issues can be reported to [email protected].