---
title: "Rest + schedule context for a team"
method: GET
path: "/v1/teams/{id}/schedule-context"
tags: ["teams"]
---

# Rest + schedule context for a team

`GET /v1/teams/{id}/schedule-context`

## Request

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

Fatigue/rest context as of a date: days of rest, the last 5 games, games in the trailing 7 days, whether the team is on a back-to-back, and the current home/away streak. **Edge plan or higher**: a model-ready rest/fatigue feature vector; Free / Solo / Trio receive a 403 naming the tier and linking the docs and pricing pages.

## Path parameters

- `id` string, uuid, required: A stored BigBalls id. This is the identifier every match, team, player and league endpoint returns, and the one every `{id}` path segment accepts. Take it from the `id` field of the corresponding list endpoint and use it as-is.

## Query parameters

- `date` string
- `tz` string

## Response `200`

ok. `{ data }` with team_id, as_of, days_rest, last_5_games, games_last_7_days, back_to_back and home_away_streak. No meta/error wrapper.

- object
  - `data` object, required
    - `team_id` string, uuid
    - `as_of` string
    - `days_rest` integer, nullable
    - `games_last_7_days` integer
    - `back_to_back` boolean
    - `home_away_streak` object
      - `type` string, nullable
      - `count` integer

## Other responses

- `400`: Invalid team id or date.

---

[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)