The broadcast object for every live match (ULTRA)

The same object as GET /broadcast/match/{matchId}, for every actively-live match, in one call. A ticker or a multi-match wall polls this instead of one URL per match, and it stays ONE request however many matches are live. At most 200 objects.

Same 1 Hz contract, same ETag and Cache-Control, same display-form fields, same every-key-present rule. An empty data means nothing is live right now and is the ordinary overnight answer, not a fault.

get/broadcast/live

Request

  • Base URL: https://api.livetennisapi.com/api/public/v1
  • URL: https://api.livetennisapi.com/api/public/v1/broadcast/live
  • Auth: one of:
    • HTTP bearer
    • API key in header X-API-Key

Query parameters

tourstring

Restrict to one tour, same vocabulary as ?tour= elsewhere.

Response

Every live match as a broadcast object

countinteger
served_atstring date-time

Changes

No recorded changes to this operation across all 1 revision of this API.