Migrating from API-Sports
Notes for teams switching from API-Sports (api-football, api-basketball, etc.). The biggest wins are unified auth across sports and built-in WebSocket delivery.
Key differences
- One auth across every sport, not a separate subscription per sport
- Lower per-event latency on real-time tier
- Built-in WebSocket; no need to poll
/livescoreevery few seconds - Consistent envelope:
{ <resource>: [...], meta: {...} }
Endpoint map (soccer)
| API-Sports | sportapi |
|---|---|
/fixtures?live=all | /v1/soccer/scores/live |
/fixtures/events?fixture={id} | /v1/soccer/fixtures/{id}/events |
/fixtures/lineups?fixture={id} | /v1/soccer/fixtures/{id}/lineups |
/standings?league=&season= | /v1/soccer/leagues/{id}/table |
Live events vs polling
If you were polling /livescore every 5 seconds, swap to the WebSocket and subscribe to soccer.scores.live. Same data, lower latency, no rate limit impact.