teams

Rest + schedule context for a team

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.

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

Path parameters

idstring 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.

Example:cf2d81c8-8e7c-4eaf-a515-c51be3962e57

Query parameters

datestring

Reference date (YYYY-MM-DD), a UTC calendar day. Defaults to today (UTC).

tzstring
Example:America/New_York

Optional IANA time zone name (e.g. America/New_York). The reference date, today, and the calendar days behind days_rest, back_to_back and games_last_7_days then use local days in that zone. Offsets such as -05:00 are rejected with 400. Example: ?date=2026-09-13&tz=America/New_York.

Response

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.

Changes

No recorded changes to this operation across all 3 revisions of this API.