---
title: "Team Elo rating history (trend line)"
method: GET
path: "/v1/teams/{id}/elo/history"
tags: ["teams"]
---

# Team Elo rating history (trend line)

`GET /v1/teams/{id}/elo/history`

## Request

- Base URL: `https://api.bigballsdata.com`
- URL: `https://api.bigballsdata.com/v1/teams/{id}/elo/history`
- Auth: one of:
  - API key in header `x-api-key`
  - HTTP bearer

Elo rating trend for a team: a baseline seed (match_id null) plus one
point per settled match, ordered oldest first. The trend sibling of
/v1/teams/{id}/elo. Response array item keys: date, elo_rating, match_id,
opponent. source selects the rating series; when omitted it is derived
from the team's own league, so an NCAAF team gets source=ncaaf and an
NFL team source=nfl without asking. Pass source explicitly to override.
A league carrying no mapping falls back to wc2026 and returns an empty
data: [], which reads as "no history" when it actually means "wrong
series"; MLB is in that position today, so pass source=mlb for a
baseball team. Optional from / to date filters. 1-hour Redis cache.
**Solo plan or higher**: Elo trend history starts at Solo; Free
receives a 403 naming the tier and linking the docs and pricing pages.

## Path parameters

- `id` string, uuid, required

## Query parameters

- `source` 'ncaaf' | 'ncaaf-fcs' | 'nfl' | 'mlb' | 'epl' | 'laliga' | 'seriea' | 'bundesliga' | 'ligue1' | 'wc2026'
- `from` string, date
- `to` string, date

## Response `200`

ok

- object

## Other responses

- `400`: invalid team id or query
- `403`: plan_required (Solo or higher)

---

[API](https://skmtc.dev/bigballsdata/apis/big-ball-sports-api.md) · [All operations](https://skmtc.dev/bigballsdata/apis/big-ball-sports-api/llms.txt) · [OpenAPI document](https://skmtc.dev/bigballsdata/apis/big-ball-sports-api/revisions/31fb54ac414e?raw)