Base URL
Authentication
Same as all other sports — pass your API key in thex-api-key header:
Table Tennis-Specific Notes
- Best of 5 or 7 games — each game to 11 points (deuce at 10-10, must win by 2)
- Score fields —
period1throughperiod7represent individual game scores - Point-by-point — available for live matches via
/match/:id/point-by-point - No current-server indicator —
score.servingis returned as-1for table tennis and there is nofirstToServefield; only aggregate service stats are available via/match/:id/statistics - No match clock —
startTimestampis the scheduled start; derive elapsed time from the firststatus.type: "inprogress"transition you observe - Live updates — subscribe to
match:{matchId}on the V2 WebSocket for per-point score pushes (measured 140–760 ms) - Events — MS/WS (singles), MD/WD (doubles), XD (mixed doubles)
- Player traits — playing hand (R/L), grip style (shakehand/penhold)
- High volume — 2,283+ matches per day — use pagination and filters
- 9 categories globally
Test IDs
Endpoint Summary
Example Requests
UI Design Ideas
- Score display: Show game-by-game scores (e.g., 3-1 with 11-8, 7-11, 11-5, 11-9)
- Match format: Best of 5 games (most events), best of 7 (World Championships finals)
- Games to 11 points (must win by 2), deuce at 10-10
- Point-by-point: Available for live matches — great for real-time tracking
- Player profile: Nationality, world ranking, playing hand (R/L), grip style (shakehand/penhold)
- High volume: 2,283+ matches per day — use pagination and filters