> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nextsportsapi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# IDs, Seasons, and Timezones

> Use stable IDs and filters consistently across football endpoints.

Most football endpoints are built around stable IDs and season filters.

## IDs

Use discovery endpoints before storing IDs in your application:

* `GET /v1/football/countries`
* `GET /v1/football/leagues`
* `GET /v1/football/teams`

League, team, fixture, venue, and player IDs returned by this API are NextSportsAPI public IDs. Treat them as stable identifiers. Names, logos, venue names, country metadata, and coverage fields can change over time.

## Seasons

Football seasons use a four-digit year, for example `2026`.

For many competitions, the season value is the year the season starts. Always confirm supported seasons with:

```http theme={"system"}
GET /v1/football/leagues/seasons
```

or by checking the `seasons` array returned by:

```http theme={"system"}
GET /v1/football/leagues?id=L7K9Q2R
```

## Timezones

Fixture endpoints can accept a `timezone` query parameter. Use a valid timezone from:

```http theme={"system"}
GET /v1/football/timezone
```

Example:

```bash theme={"system"}
curl --request GET \
  "https://api.nextsportsapi.com/v1/football/fixtures?date=2026-08-16&timezone=Asia/Tokyo" \
  --header "Authorization: Bearer YOUR_API_KEY"
```