Teams
Team fixtures
GET/v2/teams/{id}/fixturesAll plans
A page of the team’s recent or upcoming fixtures.
A known team with nothing in the list answers 200 with an empty array. One rule for every competitor list (since 2026-10-24): upcoming = not started (or postponed to a date ahead), soonest first — page 0 also picks up a next match the source files under recent (tennis players, fighters); recent = in play, finished or called off, newest first on every page. The status, score and clock of a match in play (or just finished) are current to the second; a match that kicks off appears in recent on the next request, and both lists are refreshed on the first request after one of the team’s matches ends, is moved or is postponed (see Data freshness).
Parameters
id
our numeric id (positive integer)
type
recent | upcoming (default upcoming)
page
page index, an integer 0–50 (default 0)
Response
- data
Fixture[]- meta
- type, page, count, hasNextPage
- errors
- 400 bad_request — type not recent|upcoming, or page not an integer 0–50
Every /v2 call can also answer the common errors.
$ curl -H "Authorization: Bearer sk_live_…" \ "https://api.sportsapi.app/v2/teams/{id}/fixtures"
Example
{ "data": [ { "id": 202006, "status": { "type": "finished", … }, … } ], "meta": { "type": "recent", "page": 0, "count": 30, "hasNextPage": true } }