API v2: source health, programme listings and fixture evidence on the gateway
The gateway now serves more v2 reads and accepts optional scheduling filters. Existing requests are unchanged.
New gateway reads
/api/v2/source-health: completed source-refresh information by market and sport./api/v2/broadcasts: programme listings./api/v2/matches/{id}/availability: fixture availability./api/v2/matches/{id}/schedule-evidence: fixture scheduling evidence.
Where an endpoint requires a market, use market=GB or market=IE, as for existing v2 reads.
The opt-in parameters include_unscheduled, include_unknown_time and unknown_time_cursor are also accepted on the documented endpoints. Boolean values must be true or false; the unknown-time cursor requires include_unknown_time=true.
Compatibility
These additions are optional. API keys, existing requests and default responses are unchanged. Retired v1 paths still return 410 at the gateway.
See the v2 reference and examples for market parameters and the scheduling filters supported by each endpoint.