Skip to main content
The Scores family is the heart of V1. Each endpoint returns the same game shape so you only build one renderer.

Endpoints

Baseball: use /api/v1/baseball/all instead of /api/v1/baseball/live — the live endpoint is intentionally disabled for baseball because the round structure makes “live” ambiguous between innings. The all payload already filters to in-progress games via statusGroup === 3.

Per-sport examples

Game object (real sample)

Trimmed from /api/v1/football/all:

Useful fields

Date-range query

Dates are inclusive and interpreted in UTC. The response contains the same games[] shape plus a paging object — page through with ?page=N.

Incremental polling

Every scores payload includes lastUpdateId. To avoid re-downloading identical data:
For sub-second latency, prefer the WebSocket.
Last modified on June 29, 2026