For live scoreboards and second-screen apps

A live scoreboard API. A page load and a live update that always agree.

Scores, clock, period and the game situation for 10 leagues. Load the page over REST, hand its seq to the stream, and every change after that arrives in order.

What a scoreboard needs from the data

  • One request for a whole slate

    GET /v1/{league}/games?date= returns a day's games with the teams they reference, so one request renders the board.

  • The situation, not just the score

    live_state has the period and clock, plus down, distance and yard line in football, the match minute and stoppage time in soccer, and the shootout score in hockey.

  • No gap between load and live

    Every REST response has a seq. Subscribe with it as the resume point and you get exactly the changes after what you rendered.

  • Same JSON on both paths

    REST and the WebSocket return the same entities, so the code that renders a page load also applies a live change.

Load, then follow

Read the day's games, render them, and subscribe to each game you show with the seq its response carried. Your server holds the key and the connection, and your app talks to your server.

The live state below is Bills at Vikings with 7:02 left in the 4th quarter: Bills ball, 1st and goal at the Minnesota 5. Its response is at seq 1101.

A day's games
curl "https://api.statpad.dev/v1/nfl/games?date=2026-11-09" \
  -H "Authorization: Bearer $STATPAD_API_KEY"
GET /v1/nfl/games/{id} · live_state at seq 1101Full file
{
  "away_score": 13,
  "basketball": null,
  "clock_running": null,
  "clock_seconds": 422,
  "football": {
    "away_timeouts": 3,
    "down": 1,
    "home_timeouts": 2,
    "yardline": 95,
    "yards_to_go": 5
  },
  "game_id": "01a1d60f-67be-7bdd-83f4-53286521d9bb",
  "home_score": 6,
  "last_play_id": "01a1d60f-8d90-7a74-8905-46b0dc0d2751",
  "period": 4,
  "period_half": null,
  "possession_team_id": "01a1d60f-67be-7bdf-ac2f-bcdeeac1da68",
  "soccer": null,
  "updated_at": "2026-11-13T17:58:25.937181Z",
  "version": 264
}

Pricing

A scoreboard that refreshes on a timer fits Developer. Pushing every change to your users needs the stream: Pro carries 20 subscriptions and Business 150.

Compare every limit
  • Developer

    $19 a month

    • 25,000 requests a month
    • 1 request a second, burst of 10
    • REST only, no WebSocket
  • Pro

    $49 a month

    • 150,000 requests a month
    • 10 requests a second, burst of 30
    • WebSocket: 5 connections, 20 subscriptions
  • Business

    $299 a month

    • 2,000,000 requests a month
    • 25 requests a second, burst of 100
    • WebSocket: 10 connections, 150 subscriptions

Questions

How fresh is the data?

Statpad doesn't publish a latency figure yet. When it does, it will publish the measured number per league with the date it was measured.

Can I connect browsers to the stream directly?

Keep your key on your server and fan out to your users from there. Account connections are limited per plan, so one server connection should serve many users.

Do you have team logos?

No. Statpad doesn't serve league or team logos.