Team fixtures
GET
/
View as MarkdownTry in Playground →
Returns one page of a team’s fixtures, either recent or upcoming.
If the team exists but has nothing to list, the response is 200 with an empty array. Since 2026-10-24 every competitor list splits matches the same way. upcoming holds matches not yet started (including ones postponed to a future date), soonest first, and page 0 also includes a next match that the source has filed under recent (tennis players, fighters). recent holds live, finished and called-off matches, with the newest at the top of every page. For a live or just-finished match, status, score and clock are accurate to the second. Once a match kicks off it moves to recent on your next request, and both lists are rebuilt on the first request after any of the team’s matches ends, is rescheduled or is postponed (see Data freshness).
Parameters
idpathrequired
DataSportsAPI team id, a positive integer
typequery
recent | upcoming; upcoming when omitted
pagequery
zero-based page number, a whole number from 0 to 50 (defaults to 0)
Response
- data
Fixture[]- meta
- type, page, count, hasNextPage
- errors
- 400
bad_request— type is neither recent nor upcoming, or page is not a whole number between 0 and 50
Any /v2 call can also come back with one of the common errors.
curl -H "Authorization: Bearer sk_live_…" \
"https://api.datasportsapi.com/v2/teams/{id}/fixtures"Example
{ "data": [ { "id": 202006, "status": { "type": "finished", … }, … } ],
"meta": { "type": "recent", "page": 0, "count": 30, "hasNextPage": true } }