Reference Data

Use raw and historical surfaces intentionally.

These endpoints stay closer to table-shaped rows, historical exports, assets, and stat-heavy research surfaces. They are powerful, but they are not the default starting point for most app integrations.

Reference Data

Raw, Historical, And ETL-Oriented Groups

Reach for these groups when you are doing ETL, warehousing, analytics, asset retrieval, or historical research. If you are building a product surface, the curated endpoint families are usually the better first stop.

Best For

ETL And Warehouse Loads

Use these routes when you want flatter, table-like records that can be pulled into pipelines, notebooks, or reporting layers without reshaping app-facing objects first.

Best For

Historical Research

Reach for the history surfaces when you need stadium changes, logo history, official records, venue context, or older season-linked reference rows across time.

Use Carefully

Not The Default Product Surface

If a curated endpoint already exists for teams, players, games, seasons, staff, contributors, or executives, start there first and use reference data only when you truly want the raw row shape.

Main Families

Assets, History, Reference, And Stats

The raw surface is concentrated in four groups: static assets, historical tables, reference rows, and stats-heavy exports for research-oriented workflows.

22Reference or raw endpoints
4Reference families
4Assets and history routes
18Reference and stats routes
GETCurated
/api/v1/assets/images

List curated image assets

Best For

Direct asset discovery for logos or image catalogs.

Operation ID: listImageAssets

Parameters

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

NameInWhat it meansTypeRequiredExample
groupqueryall|brand|playersnobrand
searchquerystringnologo
limitqueryMaximum number of rows to return in one response.integerno50
offsetqueryNumber of rows to skip before returning results. Use with limit for pagination.integerno0

Example Request

GET /api/v1/assets/images?limit=50

Example Response

{
  "data": [
    {
      "id": "brand-nflmeta-logo",
      "group": "brand",
      "key": "nflmeta_logo",
      "label": "NFLMeta Logo",
      "url": "https://nflmeta.org/hero_main/NFLMeta_Logo.png",
      "source": "local"
    }
  ],
  "meta": {
    "total": 11,
    "limit": 100,
    "offset": 0,
    "returned": 1,
    "has_more": false,
    "groups": [
      "all",
      "brand",
      "players"
    ]
  }
}
GETCurated
/api/v1/assets/logos

List logo assets

Best For

Direct asset discovery for logos or image catalogs.

Operation ID: listLogoAssets

Parameters

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

NameInWhat it meansTypeRequiredExample
categoryqueryall|team|season|super_bowl|stadiumnoteam
searchquerystringnosteelers
limitqueryMaximum number of rows to return in one response.integerno50
offsetqueryNumber of rows to skip before returning results. Use with limit for pagination.integerno0

Example Request

GET /api/v1/assets/logos?limit=50

Example Response

{
  "data": [
    {
      "id": "team-pit",
      "category": "team",
      "key": "PIT",
      "label": "Pittsburgh Steelers",
      "url": "https://nflmeta.org/hero_main/logos/pittsburgh-steelers-logo-transparent.png",
      "source": "local"
    }
  ],
  "meta": {
    "total": 32,
    "limit": 100,
    "offset": 0,
    "returned": 1,
    "has_more": false,
    "categories": [
      "all",
      "team",
      "season",
      "super_bowl",
      "stadium"
    ]
  }
}