Tennis Scraper — ATP, WTA | Live Scores, Odds, Point by Point
Pricing
from $0.78 / 1,000 match with score and competitions
ATP, WTA, ITF and Challenger tennis: per-set statistics, point-by-point sequences, head-to-head, live scores down to the point in play and odds from up to 20 bookmakers per country. Current rankings, tournament level and seeds. Season archives decades deep. No login, no browser.
New fields and options; nothing is removed, and the one renamed input field still accepts its old name.
dateFrom, dateTo and a tournament in tours, the run reads that tournament's season archives (see Date ranges in the README).startTimeKnown next to startTime: false for archive records the source keeps without a start time. Those have startTime null and startDate set to the day of the match, and dateFrom and dateTo compare that day.channelId, bookmakerId and countryHint on each item, url null for the source's partner links. match-broadcasts is charged only when at least one TV channel is listed.openingHome, homeDirection and the rest), and how many bookmakers hold each price above or below their first one (homeUpBookmakers and the rest).odds, and the free parts (bookmaker streams) no longer make a match changed.includeLive or the Live now filter, status, period and clock follow the live feed: a match that ended after the daily list was read comes as finished.onlyWithOdds checks up to twice as many candidates as maxMatches (was four times): in a run over the whole window 93% of tennis matches had prices.notOutputMatchIds in RUN_SUMMARY holds only matches that were not charged.monitorKey is renamed monitorName. The old name is still accepted wherever it was (runs, saved tasks, schedules, Standby queries): the same value keeps the same monitor memory, and when both are set monitorName is used.Monitor mode after the update: a match the monitor remembers from 1.0 is output once more, and billed for the base event, when its record changed shape: TV listings from the new source (with includeBroadcasts, also match-broadcasts). It happens once per match; matches whose records did not change are not output again.
The record and every view are described in the README (Output fields, Getting a spreadsheet) and in the dataset schema. Changes of the output since the 0.1 test builds:
startDate, startTime and timezone (the run's time zone), homeTeam, awayTeam, homeScore, awayScore; scrapedAt is the moment the record was output.seedNumber and entryType next to seed; fields of team sports (countryId, overtimeScore, penaltyShootout, setsWon, lineups) are no longer output.impliedHome, impliedDraw, impliedAway instead of the impliedProbability object; best price per outcome with its bookmaker, average opening prices and bookmakersCount; bookmaker rows homePrice, drawPrice, awayPrice instead of home, draw, away; price list rows price instead of odds; movement.homeDirection instead of movement.direction; numeric handicap lines; American prices with oddsFormat.homeText and awayText instead of home and away, with isHeadline; head-to-head rows homeName and awayName instead of home and away.minuteNumber, addedTime and shootoutOrder; lineups with confirmed, numeric rating and numberInt; live.clockStale.monitorChangedFieldsText, and odds.previous with odds.changePct.unavailableParts can name odds (also when one of several oddsCountries did not answer) and the box score, with unavailablePartsText next to it; RUN_SUMMARY can have status: "timing-out" and, with onlyWithOdds, scanned.meetingId, meetingTournament, meetingHomeScore, meetingAwayScore, meetingWinner and meetingStatus instead of matchId, tournament, homeScore, awayScore, winner and status, which the Head-to-head view mixed up with the match itself.live.minuteNumber and live.addedTime, substitutedAtMinuteNumber and cameOnAtMinuteNumber in lineups, numberInt in box-score lines; American prices also on the in-play averages.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.