Core Endpoints

Use the curated endpoint families first.

These are the primary app-facing surfaces for teams, players, coaches, games, seasons, and playoffs. Most integrations should start here before reaching for raw or historical exports.

Docs Overview Search Docs OpenAPI FAQ

Core Endpoints

Primary Curated Endpoint Groups

These groups are the main app-facing surfaces for object reads and filtered list workflows. They are the best starting point for production integrations that want predictable shapes.

Specialist Slice

Kicking And Punting Now Have Dedicated Player Season Endpoints

If you need specialist season rows without digging through broader stat payloads, use /api/v1/players/{player_key}/kicking and /api/v1/players/{player_key}/punting, then switch to the /{season_year} and /{field} drilldowns when the client only needs one season or one stat.

People Expansion

Staff, Contributors, Executives, And Hall Of Fame Ballots Follow The Same Slice Model

Use /api/v1/staff, /api/v1/contributors, /api/v1/executives, and /api/v1/hall-of-fame for browse flows, then switch to the structured profile or election-year drilldowns when the client needs one person or one ballot year.

Best For

App-Facing Object Reads

These groups are the primary surface for product integrations that need stable objects, browse lists, and predictable drilldowns without reconstructing the data from raw exports.

Common Pattern

List, Profile, Slice, Then Field

The normal progression is list or search first, then the object profile, then a smaller slice, and finally a /{field} drilldown when the client only needs one value.

Included Here

Teams, People, Games, Seasons, And Playoffs

This page covers the main production-facing families, including teams, players, coaches, staff, contributors, executives, games, seasons, and Hall of Fame ballot reads.

Use Raw Later

Reference Data Is Usually A Second Step

Move to raw or historical endpoints only when the curated routes no longer fit the job, such as ETL loads, table-shaped research workflows, or deeper archival joins.

99Core endpoints

15Curated families

Core Search

Filter Endpoint Groups

Search by path, summary, operation, or parameter to narrow the reference without scanning every group manually.

Showing all endpoint groups

GETCurated

/api/v1/coaches/{coach_key}

Get curated coach profile

Returns a structured coach resource with identity, bio, career, and history slices.

Best For

Coach profile pages and direct coach drilldowns.

Use Instead Of

/api/v1/coaches/{coach_key}/bio/{field} when you only need one field rather than the full object.

Operation ID: getCoachProfile

Parameters

Path parameters are part of the URL itself. Query parameters are optional filters you add after a ?.

Name	In	What it means	Type	Required	Example
`coach_key`	path	Stable coach key used by NFLMeta.	`string`	yes	`mike-tomlin`

Example Request

GET /api/v1/coaches/mike-tomlin

Example Response

{
  "data": {
    "identity": {
      "coach_key": "mike-tomlin",
      "display_name": "Mike Tomlin",
      "source_name": "Mike Tomlin",
      "photo_path": "/media/coach-photos/custom/mike-tomlin.jpg?v=1",
      "hall_of_fame": false,
      "rank": 12
    },
    "bio": {
      "birth_date": "1972-03-15",
      "birth_place": "Hampton, Virginia",
      "college_name": "William & Mary",
      "playing_position": "WR"
    },
    "career": {
      "first_year": 2007,
      "last_year": 2025,
      "regular_wins": 183,
      "playoff_wins": 8,
      "super_bowls": 1
    },
    "history": {
      "history": [],
      "awards": [],
      "team_records": [],
      "stadium_summaries": []
    }
  }
}

GETCurated

/api/v1/coaches/{coach_key}/bio

Get coach bio slice

Returns birth, college, playing-background, and narrative bio fields for one coach.

Best For

Coach bio and background reads without pulling the full profile.

Use Instead Of

/api/v1/coaches/{coach_key}/bio/{field} when you only need one field rather than the full object.

Operation ID: getCoachBio

Parameters

Path parameters are part of the URL itself. Query parameters are optional filters you add after a ?.

Name	In	What it means	Type	Required	Example
`coach_key`	path	Stable coach key used by NFLMeta.	`string`	yes	`mike-tomlin`

Example Request

GET /api/v1/coaches/mike-tomlin/bio

Example Response

{
  "data": {
    "birth_date": "1972-03-15",
    "birth_place": "Hampton, Virginia",
    "college_name": "William & Mary",
    "playing_position": "WR",
    "played_in_nfl": false
  }
}

GETCurated

/api/v1/coaches/{coach_key}/bio/{field}

Get one coach bio field

Returns a single field from the coach bio slice. Supported fields include birth_date, birth_place, death_date, death_place, college_name, playing_position, bio_summary, did_you_know, playing_career_summary, playing_college_years, pro_football_hall_of_fame_year, playing_nfl_years, playing_nfl_teams, and played_in_nfl.

Best For

Coach bio and background reads without pulling the full profile.

Operation ID: getCoachBioField

Parameters

Path parameters are part of the URL itself. Query parameters are optional filters you add after a ?.

Name	In	What it means	Type	Required	Example
`coach_key`	path	Stable coach key used by NFLMeta.	`string`	yes	`mike-tomlin`
`field`	path	—	`string`	yes	`birth_place`

Example Request

GET /api/v1/coaches/mike-tomlin/bio/birth_place

Example Response

{
  "data": {
    "field": "birth_place",
    "value": "Hampton, Virginia"
  }
}

GETCurated

/api/v1/coaches/{coach_key}/career

Get coach career slice

Returns aggregate coaching results and title metrics for one coach.

Best For

Coach career summary views and timeline-style profile sections.

Use Instead Of

/api/v1/coaches/{coach_key}/career/{field} when you only need one field rather than the full object.

Operation ID: getCoachCareer

Parameters

Path parameters are part of the URL itself. Query parameters are optional filters you add after a ?.

Name	In	What it means	Type	Required	Example
`coach_key`	path	Stable coach key used by NFLMeta.	`string`	yes	`mike-tomlin`

Example Request

GET /api/v1/coaches/mike-tomlin/career

Example Response

{
  "data": {
    "first_year": 2007,
    "last_year": 2025,
    "years_total": 19,
    "regular_games": 306,
    "regular_wins": 183,
    "playoff_games": 18,
    "playoff_wins": 8,
    "championships": 1,
    "super_bowls": 1
  }
}

GETCurated

/api/v1/coaches/{coach_key}/career/{field}

Get one coach career field

Returns a single field from the coach career slice. Supported fields include first_year, last_year, years_total, regular_games, regular_wins, regular_losses, regular_ties, regular_win_pct, playoff_years, playoff_games, playoff_wins, playoff_losses, playoff_win_pct, championships, super_bowls, conference_titles, average_rank, and best_rank.

Best For

Coach career summary views and timeline-style profile sections.

Operation ID: getCoachCareerField

Parameters

Path parameters are part of the URL itself. Query parameters are optional filters you add after a ?.

Name	In	What it means	Type	Required	Example
`coach_key`	path	Stable coach key used by NFLMeta.	`string`	yes	`mike-tomlin`
`field`	path	—	`string`	yes	`regular_wins`

Example Request

GET /api/v1/coaches/mike-tomlin/career/regular_wins

Example Response

{
  "data": {
    "field": "regular_wins",
    "value": 183
  }
}

GETRaw

/api/v1/coaches/{coach_key}/history

Get coach history slice

Returns team history, award summaries, team-record stints, and stadium summaries for one coach.

Best For

Coach profile pages and direct coach drilldowns.

Operation ID: getCoachHistory

Parameters

Path parameters are part of the URL itself. Query parameters are optional filters you add after a ?.

Name	In	What it means	Type	Required	Example
`coach_key`	path	Stable coach key used by NFLMeta.	`string`	yes	`mike-tomlin`

Example Request

GET /api/v1/coaches/mike-tomlin/history

Example Response

{
  "data": {
    "history": [
      {
        "season_year": 2025,
        "team_abbr": "PIT",
        "team_name": "Pittsburgh Steelers"
      }
    ],
    "awards": [
      {
        "award_name": "AP Coach of the Year",
        "award_count": 1,
        "first_year": 2008,
        "last_year": 2008
      }
    ],
    "team_records": [
      {
        "team_abbr": "PIT",
        "first_year": 2007,
        "last_year": 2025,
        "wins": 183,
        "losses": 107
      }
    ],
    "stadium_summaries": [
      {
        "team_abbr": "PIT",
        "first_year": 2007,
        "last_year": 2025,
        "stadium_names": "Acrisure Stadium"
      }
    ]
  }
}

GETCurated

/api/v1/coaches/{coach_key}/identity

Get coach identity slice

Returns name, photo, Hall of Fame, and rank fields for one coach.

Best For

Coach identity cards, profile headers, and canonical coach facts.

Use Instead Of

/api/v1/coaches/{coach_key}/identity/{field} when you only need one field rather than the full object.

Operation ID: getCoachIdentity

Parameters

Path parameters are part of the URL itself. Query parameters are optional filters you add after a ?.

Name	In	What it means	Type	Required	Example
`coach_key`	path	Stable coach key used by NFLMeta.	`string`	yes	`mike-tomlin`

Example Request

GET /api/v1/coaches/mike-tomlin/identity

Example Response

{
  "data": {
    "coach_key": "mike-tomlin",
    "display_name": "Mike Tomlin",
    "source_name": "Mike Tomlin",
    "photo_path": "/media/coach-photos/custom/mike-tomlin.jpg?v=1",
    "hall_of_fame": false,
    "rank": 12
  }
}

GETCurated

/api/v1/coaches/{coach_key}/identity/{field}

Get one coach identity field

Returns a single field from the coach identity slice. Supported fields include coach_key, display_name, source_name, photo_path, hall_of_fame, and rank.

Best For

Coach identity cards, profile headers, and canonical coach facts.

Operation ID: getCoachIdentityField

Parameters

Path parameters are part of the URL itself. Query parameters are optional filters you add after a ?.

Name	In	What it means	Type	Required	Example
`coach_key`	path	Stable coach key used by NFLMeta.	`string`	yes	`mike-tomlin`
`field`	path	—	`string`	yes	`display_name`

Example Request

GET /api/v1/coaches/mike-tomlin/identity/display_name

Example Response

{
  "data": {
    "field": "display_name",
    "value": "Mike Tomlin"
  }
}