How playerWON gets and uses its data
playerWON combines publicly available NHL data with sportsbook odds data to power schedules, stats, matchup pages, model predictions, and betting tools.
We believe in being transparent about our sources so users can understand what powers the site and explore the data themselves.
NHL data
Used for schedules, standings, team stats, boxscores, player pages, game logs, and model features.
Odds data
Used for sportsbook comparisons, fair odds, implied probability, edge calculations, and EV tools.
Model outputs
Our predictions are generated from our own processing and modeling of these source datasets.
🏒 NHL Data Sources
These endpoints power the NHL stats, standings, schedules, players, and game-level information shown across playerWON.
📅 Seasons Metadata
Used to identify season boundaries and support season-based logic.
https://api-web.nhle.com/v1/standings-season
📊 Current Standings
Used for up-to-date standings, team positions, and playoff race context.
https://api-web.nhle.com/v1/standings/now
📆 Historical Standings by Date
Used to retrieve standings on specific dates for historical analysis and season snapshots.
https://api-web.nhle.com/v1/standings/YYYY-MM-DD
🏒 Game Schedule & Game IDs
Used to retrieve schedules, matchup details, and the game IDs needed for deeper game data pulls.
https://api-web.nhle.com/v1/schedule/YYYY-MM-DD
📦 Game Boxscores
Returns detailed game information including team scoring, player stats, goalie stats, and shot totals.
https://api-web.nhle.com/v1/gamecenter/{gameId}/boxscore
🧍 Player Metadata
Provides player information such as position, handedness, height, weight, birthplace, and current team.
https://api-web.nhle.com/v1/player/{playerId}/landing
📁 Team Metadata
Lists active NHL teams with official IDs, names, and abbreviations.
https://api.nhle.com/stats/rest/en/team
📈 Historical Team Stats
Used for season-level team stats, historical comparisons, and model feature generation.
https://api.nhle.com/stats/rest/en/team/summary?cayenneExp=seasonId={seasonId} and gameTypeId=2
💰 Odds API Data Sources
These endpoints power sportsbook odds comparisons and betting-related tools on playerWON.
🎯 Sports List
Used to identify supported sports and their sport keys before querying odds endpoints.
https://api.the-odds-api.com/v4/sports/?apiKey=YOUR_API_KEY
📋 Current Odds
Used to retrieve upcoming event odds from bookmakers 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
🕘 Historical Odds Snapshots
Used to retrieve historical odds snapshots for model evaluation, backtesting, and odds history analysis.
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
🧾 Betting Markets
Used to determine which market types are available, such as head-to-head, spreads, and totals.
Examples: h2h, spreads, totals
How playerWON uses odds data
- Compare sportsbook prices against our model probabilities
- Convert odds into implied probability
- Calculate fair odds from model probabilities
- Estimate edge and expected value
- Support betting dashboards and market comparison pages
⚙️ How this data becomes playerWON content
We retrieve publicly available NHL data and market odds data from external APIs.
The raw data is processed and stored in our own database for fast access and historical tracking.
We clean, combine, and structure the data into tables, pages, summaries, and model-ready features.
The processed results are shown on playerWON as schedules, standings, predictions, stats, and betting tools.
⚠️ Data Disclaimer
All data displayed on playerWON is retrieved from third-party public or licensed API sources and then processed into our own database, views, and model outputs.
While we update our pipelines regularly, we do not guarantee that all source data is free from delays, inconsistencies, omissions, or live-update issues.
If you notice something that looks incorrect, please contact us at [email protected] and we’ll investigate.