Tournament Endpoints (10)
All endpoints use base URLhttps://api.sportsapipro.com/v2/table-tennis.
Tournament Info
Season-Specific Endpoints
All requiretournamentId + seasonId. Discover season IDs via /api/tournament/:id/seasons.
/draw vs /rounds — Format Support
/draw and /rounds are not interchangeable. Each is populated only for specific tournament formats. Call /api/tournament/:id/info first and branch on hasRounds.
Format support matrix
Rule of thumb:
hasRounds: true → use /rounds; hasRounds: false → use /draw. Knockout tournaments returning 404 on /rounds is a permanent upstream limitation, not a bug.
Preflight check
/draw — example 200 response (tournament 21417, season 90349)
/rounds — example 200 response (league format)
Response / error codes
Example: TT Elite Series (Poland)
Unique tournament19041 (category Poland 1340, men), season 2026 96789. It’s very busy, with hundreds of matches a day.
To discover matches, poll
/api/today or /api/schedule/:date and keep events where tournament.uniqueTournament.id === 19041.