Developer Reference

NFLMeta API

A structured docs system for onboarding, authentication, identifier discovery, core endpoints, raw reference data, recipes, and API changes.

121Documented endpoints
19Endpoint groups
110Curated routes
11Raw or mixed routes
Public Docs

Open Without Login

These pages are public so developers can evaluate the product and plan integrations before account setup.

  • /installation
  • /api-docs
  • /api-docs/sdk
  • /faq
  • /openapi.yaml
Protected API

Call With API Key

Versioned endpoints under /api/v1/* are reachable directly and enforce route-level API key auth through X-NFLMeta-Key.

  • 401 without a key
  • 200 with a valid key
  • Rate and quota headers on protected responses
Overview

Start With The Docs Path, Not The Endpoint Dump

New users should go in this order: quickstart, authentication, identifier discovery, then the endpoint family that matches the integration. If you are using TypeScript/JavaScript or Python, fold the SDK docs into that path before you build your own client wrapper. The full OpenAPI surface is still here, but it no longer needs to be the first thing someone reads.

Start Here

Start with one team object

Best first request if you want to confirm auth, inspect shape, and understand the slice-and-field model.

/api/v1/teams/NE
Start Here

Fetch one single field

Best first drilldown request when you want the smallest stable payload possible.

/api/v1/season/2024/champion_team_abbr
Start Here

Inspect one full game object

Best first app-style payload if your integration is schedule, recaps, matchups, or game detail heavy.

/api/v1/games/11565
Start Here

Pull one raw reference row

Best first raw export request if you are evaluating warehouse or ETL-style access.

/api/v1/reference/venues/geha-field-at-arrowhead-stadium
Consumer Rule

Use the Narrowest Object Endpoint First

If the use case is about one player, team, coach, season, or game object, start with the smallest slice that already matches that domain.

Example: Examples: /api/v1/players/{player_key}/identity, /api/v1/coaches/{coach_key}/career, /api/v1/staff/{staff_key}/bio, /api/v1/contributors/{contributor_key}/bio, /api/v1/teams/{abbr}/stadium

Consumer Rule

Use Drilldowns for One Field

When the client only needs one value, prefer the synchronized /{field} variant instead of pulling the full object and trimming it client-side.

Example: Examples: /api/v1/teams/{abbr}/identity/city, /api/v1/games/{id}/stadium, /api/v1/season/{year}/winner

Consumer Rule

Use Raw or Composite Only Intentionally

Reach for composite endpoints when you want richer joined payloads, and use /reference or stats-heavy raw exports when you need near-table data for ETL or research.

Example: Examples: /api/v1/games/{id}/extras for app-ready joins, /api/v1/reference/venues/{venue_key} for raw records

Curated

Assets Endpoints

Best for: Assets integrations across 2 published endpoints.

Generated directly from the OpenAPI spec. This section currently includes 2 endpoints covering assets workflows.

  • /api/v1/assets/images
  • /api/v1/assets/logos
Mixed

Coaches Endpoints

Best for: Coaches integrations across 8 published endpoints.

Generated directly from the OpenAPI spec. This section currently includes 8 endpoints covering coaches workflows.

  • /api/v1/coaches/{coach_key}
  • /api/v1/coaches/{coach_key}/bio
  • /api/v1/coaches/{coach_key}/bio/{field}
  • /api/v1/coaches/{coach_key}/career
  • /api/v1/coaches/{coach_key}/career/{field}
  • /api/v1/coaches/{coach_key}/history
Mixed

Contributors Endpoints

Best for: Contributors integrations across 8 published endpoints.

Generated directly from the OpenAPI spec. This section currently includes 8 endpoints covering contributors workflows.

  • /api/v1/contributors
  • /api/v1/contributors/{contributor_key}
  • /api/v1/contributors/{contributor_key}/bio
  • /api/v1/contributors/{contributor_key}/bio/{field}
  • /api/v1/contributors/{contributor_key}/history
  • /api/v1/contributors/{contributor_key}/history/{field}
Mixed

Executives Endpoints

Best for: Executives integrations across 10 published endpoints.

Generated directly from the OpenAPI spec. This section currently includes 10 endpoints covering executives workflows.

  • /api/v1/executives
  • /api/v1/executives/{executive_key}
  • /api/v1/executives/{executive_key}/bio
  • /api/v1/executives/{executive_key}/bio/{field}
  • /api/v1/executives/{executive_key}/career
  • /api/v1/executives/{executive_key}/career/{field}
Curated

Games Endpoints

Best for: Games integrations across 4 published endpoints.

Generated directly from the OpenAPI spec. This section currently includes 4 endpoints covering games workflows.

  • /api/v1/games
  • /api/v1/games/{id}
  • /api/v1/games/{id}/{field}
  • /api/v1/games/{id}/extras
Curated

Hall of Fame Endpoints

Best for: Hall of Fame integrations across 3 published endpoints.

Generated directly from the OpenAPI spec. This section currently includes 3 endpoints covering hall of fame workflows.

  • /api/v1/hall-of-fame
  • /api/v1/hall-of-fame/{election_year}
  • /api/v1/hall-of-fame/{election_year}/{field}
Curated

History Endpoints

Best for: History integrations across 2 published endpoints.

Generated directly from the OpenAPI spec. This section currently includes 2 endpoints covering history workflows.

  • /api/v1/history/stadiums
  • /api/v1/history/team-logos
Curated

Metadata Endpoints

Best for: Metadata integrations across 2 published endpoints.

Generated directly from the OpenAPI spec. This section currently includes 2 endpoints covering metadata workflows.

  • /api/v1/coaches
  • /api/v1/show
Curated

Operations Endpoints

Best for: General health lookups and app-facing reads.

Generated directly from the OpenAPI spec. This section currently includes 1 endpoint covering operations workflows.

  • /api/v1/health
Curated

Players Endpoints

Best for: Players integrations across 23 published endpoints.

Generated directly from the OpenAPI spec. This section currently includes 23 endpoints covering players workflows.

  • /api/v1/players/{player_key}/bio
  • /api/v1/players/{player_key}/bio/{field}
  • /api/v1/players/{player_key}/career
  • /api/v1/players/{player_key}/career/{field}
  • /api/v1/players/{player_key}/career/seasons
  • /api/v1/players/{player_key}/games
Curated

Playoffs Endpoints

Best for: Playoffs integrations across 4 published endpoints.

Generated directly from the OpenAPI spec. This section currently includes 4 endpoints covering playoffs workflows.

  • /api/v1/playoff-games/{id}
  • /api/v1/playoff-games/{id}/{field}
  • /api/v1/playoff-games/{id}/extras
  • /api/v1/playoffs/picture
Raw

Reference Endpoints

Best for: Reference integrations across 6 published endpoints.

Generated directly from the OpenAPI spec. This section currently includes 6 endpoints covering reference workflows.

  • /api/v1/reference/coaches/{coach_key}
  • /api/v1/reference/coaches/{coach_key}/{field}
  • /api/v1/reference/officials/{official_key}
  • /api/v1/reference/officials/{official_key}/{field}
  • /api/v1/reference/venues/{venue_key}
  • /api/v1/reference/venues/{venue_key}/{field}
Curated

Seasons Endpoints

Best for: Seasons integrations across 4 published endpoints.

Generated directly from the OpenAPI spec. This section currently includes 4 endpoints covering seasons workflows.

  • /api/v1/byes/{year}
  • /api/v1/season/{year}
  • /api/v1/season/{year}/{field}
  • /api/v1/seasons
Mixed

Staff Endpoints

Best for: Staff integrations across 10 published endpoints.

Generated directly from the OpenAPI spec. This section currently includes 10 endpoints covering staff workflows.

  • /api/v1/staff
  • /api/v1/staff/{staff_key}
  • /api/v1/staff/{staff_key}/bio
  • /api/v1/staff/{staff_key}/bio/{field}
  • /api/v1/staff/{staff_key}/career
  • /api/v1/staff/{staff_key}/career/{field}
Curated

Standings Endpoints

Best for: Standings tables and week-to-week ranking views.

Generated directly from the OpenAPI spec. This section currently includes 1 endpoint covering standings workflows.

  • /api/v1/standings
Curated

Stats Endpoints

Best for: Stats integrations across 12 published endpoints.

Generated directly from the OpenAPI spec. This section currently includes 12 endpoints covering stats workflows.

  • /api/v1/stats/players/careers
  • /api/v1/stats/players/careers/{stat}
  • /api/v1/stats/players/catalog
  • /api/v1/stats/players/compare
  • /api/v1/stats/players/games
  • /api/v1/stats/players/games/leaders/{stat_family}
Curated

Super Bowls Endpoints

Best for: Super Bowls integrations across 3 published endpoints.

Generated directly from the OpenAPI spec. This section currently includes 3 endpoints covering super bowls workflows.

  • /api/v1/super-bowls
  • /api/v1/super-bowls/{season_year}
  • /api/v1/super-bowls/teams/{abbr}
Mixed

Teams Endpoints

Best for: Teams integrations across 17 published endpoints.

Generated directly from the OpenAPI spec. This section currently includes 17 endpoints covering teams workflows.

  • /api/v1/teams
  • /api/v1/teams/{abbr}
  • /api/v1/teams/{abbr}/games
  • /api/v1/teams/{abbr}/identity
  • /api/v1/teams/{abbr}/identity/{field}
  • /api/v1/teams/{abbr}/power-rankings
Curated

Usage Endpoints

Best for: Programmatic quota and usage checks from client dashboards or internal tooling.

Generated directly from the OpenAPI spec. This section currently includes 1 endpoint covering usage workflows.

  • /api/v1/usage