Skip to main content
To avoid cross-timezone ambiguity, all time fields in AnySport use UTC, whether in query parameters or response fields. Clients are responsible for converting to the end user’s local timezone before display — the API itself performs no timezone inference or conversion.

Two time representations

You’ll notice the API uses two different levels of time granularity:
  • Separate date + time (date + time): used for fixture-related fields, where date is YYYY-MM-DD and time is HH:mm, both in UTC. When you need to combine them, concatenate them yourself, e.g. 2026-07-15T19:00:00Z.
  • A single ISO-8601 instant (with a Z suffix): used for updated_at in live feeds and meta.timestamp in the response envelope — already a complete datetime string that can be passed directly to most languages’ date-parsing functions.

Localized display example

The following examples show how to convert the UTC time returned by the API into the user’s local time:
Both request and response dates use ISO YYYY-MM-DD; time and date are both UTC — to display local time, the client must convert according to the user’s timezone. This convention applies to every endpoint in this documentation and is not repeated on each individual endpoint page.