Coverage Board
Team Stats Endpoints
Coverage board endpoints for rosters, franchise context, and team history
Team Stats Endpoints
Six endpoints assemble the franchise coverage board.
Primary route: Start with
team_idwhen you have it; use the team-year surfaces when you are still orienting across franchise history.Pair these feeds with Player Stats for individual dossiers and League Stats for season-wide context.
Quick route
| If you need... | Use | Why it is the fastest route |
|---|---|---|
| a directory of team years | CommonTeamYears | Fast way to orient on active ranges and franchise abbreviations |
| one team's current snapshot | TeamInfoCommon | Best team dossier opener for record, ranking, and conference/division context |
| ownership, arena, coach, and background detail | TeamDetails | Best source for front-office and organization context |
| a season roster and coaching staff | CommonTeamRoster | Quickest route to the people attached to one team-season |
| relocation and long-run franchise history | FranchiseHistory | Best for brand changes, defunct branches, and long-view record context |
| year-by-year statistical history | TeamYearByYearStats | Best for one franchise's season trendline across eras |
Lookup and current snapshot
| Endpoint | Parameters | Result sets | Route cue |
|---|---|---|---|
CommonTeamYears | none listed | TeamYears | Start here when you need the franchise directory or active-year bounds before choosing a team |
TeamInfoCommon | team_id (required) | TeamInfoCommon, TeamSeasonRanks | Default opener for one club's current-season identity, record, and ranking context |
Organization and roster detail
| Endpoint | Parameters | Result sets | Key columns / signals | Route cue |
|---|---|---|---|---|
TeamDetails | team_id (required) | TeamBackground, TeamHistory, TeamSocialSites, TeamAwardsChampionships, TeamAwardsConf, TeamAwardsDiv, TeamHof, TeamRetired | abbreviation, nickname, yearfounded, city, arena, arenacapacity, owner, generalmanager, headcoach | Use when the team file needs ownership, venue, honors, or retired-number context |
CommonTeamRoster | team_id (required), season (required) | CommonTeamRoster, Coaches | player roster rows plus coaching staff rows | Use when the question is about who was on the team in a specific season |
Franchise history lane
| Endpoint | Parameters | Result sets | Key columns / signals | Route cue |
|---|---|---|---|---|
FranchiseHistory | none listed | FranchiseHistory, DefunctTeams | team_id, team_city, team_name, start_year, end_year, years, games, wins, losses, win_pct, po_appearances, div_titles, conf_titles, league_titles | Use when relocation, naming, or defunct-team lineage is part of the question |
TeamYearByYearStats | team_id (required) | TeamStats | year-by-year team statistical output | Use when you want the franchise trendline rather than one-season snapshot |
Route cues
- Use
TeamInfoCommonas the default first stop for a current club file. - Add
CommonTeamRosterthe moment the question becomes “who was actually there?” - Reach for history endpoints only when the question crosses seasons, relocations, or eras.
Next steps from team coverage
Drill into the people on the roster
Move to Player Stats when the team file needs player bios, career arcs, awards, and individual dashboards behind the roster sheet.
Zoom out to season-wide competition
Use League Stats to place one franchise inside the standings, leaderboards, lineups, and matchup environment for a given season.
Connect franchise context to incoming talent
Open Draft when the next question is about pick history, class order, or combine packets tied to a team-building timeline.
Keep moving
Stay in the same possession
Keep the mental model warm with adjacent pages, section hubs, and search-friendly routes into the same topic cluster.