DEVELOPERS

One canonical event. Every downstream surface.

Build against stable match, score and timeline resources; resume live streams after disconnects; verify every webhook before accepting it.

Read the docsRequest integration access →
REST
GET /api/v1/matches/{matchId}
GET /api/v1/matches/{matchId}/score
GET /api/v1/matches/{matchId}/timeline
SERVER-SENT EVENTS
GET /api/v1/matches/{matchId}/stream
Last-Event-ID: 42
Accept: text/event-stream
SIGNED WEBHOOK
LiveStreamBlog-Event: score.changed
LiveStreamBlog-Timestamp: 1786060800
LiveStreamBlog-Signature: v1=…
01

Retry safely

Client idempotency keys and expected aggregate versions prevent duplicate or silently conflicting writes.

02

Reconnect exactly

SSE event IDs and durable replay let readers continue without polling or losing accepted events.

03

Trust deliberately

Tenant-scoped bearer credentials, explicit scopes and HMAC verification keep public output keys separate from editorial power.