League tables, season scoring charts and tennis rankings in one Actor: rank, form, goals, points, qualification zones, next fixture, top scorers with club and nationality, ATP and WTA rankings with points and position change, tennis Elo by surface. No login, no browser.
The records and every view are described in the README (Fields, Download as a
spreadsheet) and in the dataset schemas. Changes of the output since the 0.1 test builds:
tournamentId is now the league's ID, the same for every season, as in the match Actors.
The season's ID, which tournamentId used to hold, is tournamentSeasonId, and the stage's
ID, which was stageId, is tournamentStageId.
ATP and WTA rankings and Elo tables go to the run's rankings dataset, not to the default
one with the league records.
A league or ranking that holds no data comes with its error and without empty lists.
New filters overUnderLines and formWindows keep only the lines and form windows you need,
without extra requests; rankingUrls is a list of the eight ranking pages.
New views: Home table, Away table and Form, Over/Under and HT/FT; the table views
carry the league and season IDs, and Top scorers also playerId and teamId.
Table rows carry the team's logo, teamLogoUrl, read from the same feed.
A streak over all five recent results is checked in the league's form table: W6 is exact,
W10+ means ten or more; streakMin holds the length as a number.
lastSeasons and seasons return earlier seasons of a league page, one league record per
season, each billed as a league; a season the league does not have gives season not found.
onlyChanges with changesName returns and bills only the rows that are new or changed since
the previous run, marked with changeType; nested records carry unchangedRows.
maxRankingRows and maxTopScorers go up to 5,000: the whole ATP singles table is about
2,300 rows. The input form opens with the ATP top 10 instead of the ATP and WTA top 100.
When the platform restarts a run, the league seasons, rankings and Elo tables already output are
skipped and not billed again; a proxy group or country your plan does not include is named in
the run's status.
The input field changesKey is renamed changesName. The old name is still accepted wherever
it was (runs, saved tasks, schedules): the same value keeps the same memory, and when both are
set changesName is used.
From here on a field that is removed, or renamed without its old name still working, or a
default that changes, comes with a new major version. To stay on one build, pass its build
number (such as 1.0.3, shown in the run's details) as build when you start a run through
the API.