Guides
Written from running this API, not from a template. Every example uses endpoints and fields that exist today.
Build a live football score app with a free API
The full walkthrough, in the order the problems arrive: endpoints, caching, polling, the UTC boundary, lazy match detail, and watching your own quota.
Read guide →Live football scores API: matches vs scores
Two endpoints return fixtures and they are not interchangeable. Picking wrong shows an empty app or fills it with matches nobody can watch.
Read guide →has_stream and has_stats: check data before you ask
Coverage differs per competition. Four flags tell you what exists before you request it, and they ride along in responses you already make.
Read guide →Football stream embed API for live match players
Fetch the sources, mount the iframe, offer a switcher - and handle the three states that actually occur: no stream yet, a source that drops, and a match that is over.
Read guide →Head-to-head API: build a match preview page
Head-to-head, season form, last five and model probabilities make a page with real content before kick-off - exactly when people search for the fixture.
Read guide →Football standings API: build a league table
The standing endpoint returns four features, not one: the table, home and away splits, qualification colours and whether a team moved up or down.
Read guide →Football lineups API: formations and player ratings
Draw a pitch without coordinates, pick the right stats per position, and avoid the caching mistake that freezes every rating for ninety minutes.
Read guide →Switch sports data providers without breaking clients
How SportSRC swapped its upstream source between v2 and v3 while keeping the response shape identical, and the traps found on the way.
Read guide →