Real-time updates (SSE)

Live leaderboards, odds, brackets, match-play matches, and team matches are available as Server-Sent Events (SSE) streams, so you can show scores update without polling. Five streams exist:

Stream	Endpoint	Event name
Leaderboard	GET .../events/{eventSlug}/leaderboard/stream	leaderboard
Odds	GET .../events/{eventSlug}/odds/stream	odds
Bracket	GET .../events/{eventSlug}/bracket/stream	leaderboard
Team match	GET .../events/{eventSlug}/leaderboard/team-match/stream	leaderboard
Match play	GET .../events/{eventSlug}/leaderboard/match-play/stream	leaderboard

Each stream's payload is identical to its non-streaming JSON counterpart (.../leaderboard, .../odds, .../bracket, .../leaderboard/team-match, and .../leaderboard/match-play) — so you can render from one shape whether you fetched once or subscribed.

The bracket, team-match, and match-play streams are for events of type bracket, team_match, and match_play respectively (any other event type gets a 400), and push the same JSON as their GET counterparts. Note their updates also arrive under the event name leaderboard (not bracket, team-match, or match-play), so listen for leaderboard on those streams too.

Wire format

The response is Content-Type: text/event-stream. On connect you get a comment line, then a named event per update:

: connected

event: leaderboard
data: {"leaderboards":[ ... ]}

event: leaderboard
data: {"leaderboards":[ ... ]}

The leaderboard stream also accepts ?includeOdds=true to fold a winOdds column into each row.

Consuming it

In the browser, use EventSource and listen for the named event (not the default message):

const es = new EventSource(
  "https://api.front9.com/api/public/v1/orgs/acme/events/spring-classic-2026/leaderboard/stream"
);

es.addEventListener("leaderboard", (e) => {
  const data = JSON.parse(e.data);
  render(data.leaderboards);
});

es.onerror = () => {
  // EventSource auto-reconnects; close it when the user leaves the page.
};

Odds work the same way — listen for the odds event.

Tips

• Prefer the stream over polling for anything live — it's one connection and doesn't eat your rate-limit budget.
• Close the connection (es.close()) when the view unmounts.
• Odds may be unavailable. Before an event has scores, an odds payload can arrive with "status": "unavailable" and a message. Render accordingly.
• For one-off reads (server-side rendering, snapshots), just call the plain .../leaderboard or .../odds endpoint instead.