Recipes
Task-oriented guides. Each one states a goal, shows the exact sequence of calls, gives working code, and names the traps that are not visible from the reference alone.
Every code sample on these pages has been run against the production API - the payloads and values shown are real responses, not illustrations.
Start here
Section titled “Start here”| Recipe | What you get | Time |
|---|---|---|
| Get a token and make your first call | Credential exchange, token caching, first working request | 5 min |
| Display a league table | The two-step navigation from stage to rendered table | 10 min |
| Get one match with score and stats | Reading a score correctly, statistics, timeline | 10 min |
| Show a match timeline | Ordering, deduplication, corrections, added time, substitutions | 15 min |
| Build a livescore board | One polled endpoint, clock rendering, when to move to push | 15 min |
| Display a knockout bracket | Rounds, nodes and slots into a renderable tree, two-legged ties | 20 min |
| Sync incrementally instead of re-fetching | The timestamp cursor, why the boundary is inclusive | 12 min |
| Show top scorers, cards and assists | 19 ranking types, and why player rows invert participant | 12 min |
| Compare two teams head to head | All-time balance, last 10, and the five-level event tree | 8 min |
| List a team squad | Players, departed players and the coach in one array | 8 min |
| Build a season calendar | A whole season of fixtures with scores, grouped by round | 12 min |
Concepts you need first
Section titled “Concepts you need first”Four things are worth understanding before any recipe, because otherwise the sequences look arbitrary. They are spelled out in the recipes above and expanded in Concepts (sidebar lists every concept page):
- The payload is in
api.data, not at the top level - Match state needs three fields -
status_type,status_idandrelation_status. A postponed match still reportsstatus_type: "scheduled"- see season lifecycle - The clock is in seconds and resets each period.
played_timeis the cumulative total - see time, clocks and timezones - There is no
scorefield - you select a result byidfromresults[](recipe 03)
Reference catalogues
Section titled “Reference catalogues”On the portal, generated tables replace hand-maintained id lists:
| Where | Contents |
|---|---|
| Data reference | Per-sport statuses, results, statistics, incidents (from GET /v2/sports/{id}) |
| OpenAPI reference | Full REST surface, including OAuth and query parameters |