APIEndpoint referenceTournament
/tournament
Query Parameters
days?integer
Format
int64withinHours?string
upcomingFixtures?string
Response Body
application/json
application/json
curl -X GET "https://example.com/api/tournament"{ "data": { "property1": [ { "categorySlug": "string", "country": "string", "id": 0, "internalId": 0, "isFavorite": true, "name": "string", "shouldShow": true, "slug": "string", "uniqueTournamentId": 0, "uniqueTournamentSlug": "string", "upcomingFixtureCount": 0 } ], "property2": [ { "categorySlug": "string", "country": "string", "id": 0, "internalId": 0, "isFavorite": true, "name": "string", "shouldShow": true, "slug": "string", "uniqueTournamentId": 0, "uniqueTournamentSlug": "string", "upcomingFixtureCount": 0 } ] }}/tipster/preview/{id} PUT
Ownership is checked against a row read without an author filter, so a preview belonging to someone else is a 403 rather than a 404 here — unlike GET and DELETE, which scope the lookup.
/tournament/upcoming-fixtures-multi POST
The next fixtures across several competitions at once.