APIEndpoint referenceBasketball
/basketball/tournaments
The visible competitions, folded by unique tournament and then bucketed by country.
The visible competitions, folded by unique tournament and then bucketed by country.
Two rows are dropped along the way and both are deliberate. A tournament with
no unique tournament attached is skipped entirely, and a group whose country
is null never lands in a bucket. The result is that the payload can omit a
competition that should_show is true for.
name comes from the unique tournament but slug, isFavorite and
shouldShow come from whichever tournament was seen first, so a group's name
and slug can describe different rows. That is the original's behaviour.
Response Body
application/json
application/json
curl -X GET "https://example.com/api/basketball/tournaments"{ "data": { "property1": [ { "country": "string", "id": 0, "isFavorite": true, "name": "string", "shouldShow": true, "slug": "string", "uniqueTournamentId": 0 } ], "property2": [ { "country": "string", "id": 0, "isFavorite": true, "name": "string", "shouldShow": true, "slug": "string", "uniqueTournamentId": 0 } ] }}