REST API
For the fantasy manager, use a normal system API key in the x-api-key header. The recommended scope set is:
One public entry point for the fantasy manager and score integrations. This page covers the REST API surface, tournament gameplan reads, and the realtime WebSocket feed with exact payload references.
For the fantasy manager, use a normal system API key in the x-api-key header. The recommended scope set is:
Realtime subscriptions connect to a dedicated WebSocket endpoint. Authentication is done via query parameter, not via header.
Each request uses the x-api-key header unless noted otherwise. Example values are placeholders.
Backend-to-fantasy-manager calls use x-api-token. These are listed here so the request shapes can be tested independently.
WebSocket authentication uses the query string, because browser WebSocket clients cannot reliably send custom headers.
The realtime feed sends match_update for match changes and tournament_schedule_update for tournament-plan changes.