Integrate Live Scores

This is the fun part — and the most common reason to use the API. Let’s get a live score on your screen. Here’s one happening right now:

Live right now

Loading live matches…

How a score reaches you

The moment a point is scored on court, it’s all automatic — you only plug in at the very end:

flowchart LR P([Point scored<br/>on court]) -->|automatic| API2[(Match updated)] API2 -->|WebSocket / REST / QR| YOU([Your app]) classDef you fill:#6d28d9,stroke:#6d28d9,color:#fff; class YOU you;

You subscribe to (or poll) a match. Everything before that is the API's job.

You read matches — the API takes care of everything up to that point.

Three ways to receive scores

Pick whichever fits. Most apps use WebSocket for instant updates and REST as a backup.

flowchart TD Q{What do you<br/>need?} -->|Instant, lowest latency| WS[WebSocket] Q -->|Simple & cache-friendly| REST[REST polling] Q -->|On-court QR sign| QR[By the court] WS --> Done([Live scores<br/>in your app]) REST --> Done QR --> Done classDef d fill:#16a34a,stroke:#16a34a,color:#fff; class Done d;

| You want… | Use | Login? | |---|---|---| | Instant updates | Realtime / WebSocket | no (public rooms) | | Dead-simple polling | REST | no | | “What’s on this court?” (QR) | By the court | no | | Push into your backend | Push / webhooks | M2M token |

Try it right now

This is the single most useful call — every match in progress, this second. Hit the button:

GET https://api.myscore.live/api/v1/live/matches ▶ Run it live

No key, no setup — that’s a real response from the production API. 🎉

What you got back

Each match looks like this:

{
  "id": "mtch_006",
  "status": "in_progress",
  "sets": [{ "home": 6, "guest": 5 }, { "home": 3, "guest": 1 }],
  "home": { "id": "...", "name": "Roger Federer" },
  "guest": { "id": "...", "name": "Rafael Nadal" },
  "court": { "id": "...", "name": "Centre Court" },
  "tournament": { "id": "...", "name": "Summer Open" }
}

• sets is a list of { home, guest } game counts — one entry per set played.
• status moves scheduled → in_progress → completed (it can also be suspended or cancelled).

Ready? Pick a delivery method and let’s wire it up.

Realtime / WebSocket → Instant pushes the moment a score changes.

REST polling → The simplest possible integration.