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, wheredateisYYYY-MM-DDandtimeisHH: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
Zsuffix): used forupdated_atin live feeds andmeta.timestampin 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.