BDP @ Betfair wrote:Hi,
Due to a recent changes with our feed supplier, WTA tennis events will no longer be made available via the Tennis Scores API with immediate effect.
ATP events will continue to be provided as usual via the Tennis Scores API.
For a schedule of up and coming ATP events please see the ATP website (https://www.atptour.com/en/tournaments)
Kind Regards
Betfair Developer Program
Betfair Tennis Scores API - WTA Events No Longer Available
We just got an email from Betfair indicating that they are pulling the live score feed from the API for WTA events.
Disappointing to say the least
The fact that they have given no notice will mean that quite a lot will fail silently, so it will have an immediate impact. We are braced for support queries.
It's really unprofessional to announce it on the first day that the changes would have effected. Pretty shoddy.
It's really unprofessional to announce it on the first day that the changes would have effected. Pretty shoddy.
- MemphisFlash
- Posts: 1456
- Joined: Fri May 16, 2014 10:12 pm
- Location: Leicester
thats the end of my fancy excel sheets for tennis then
The only workaround I can think of is querying a stats site like Sofascore via the API and pulling the scores down that way, then passing to Guardian via a linked Excel Stored Value. I'm already doing it for in play tennis stats
Speed and number of allowed API queries per hour may be an issue. It may not work for point by point trading but swing trading could still be possible.
Also means a full rework of the Guardian BAF , unless all the rules are ported to Excel
Could also mean Tie Breaks would be tradeable
Time to get to work....
Data is there:
+-> .events[3].awayTeam.name =Andreev A.
+-> .events[3].awayTeam.slug =andreev-adrian
+-> .events[3].awayTeam.shortName =Andreev A.
+-> .events[3].awayTeam.gender =M
+-> .events[3].awayTeam.userCount =980
+-> .events[3].awayTeam.nameCode =AND
+-> .events[3].awayTeam.ranking =564
+-> .events[3].awayTeam.national =False
+-> .events[3].awayTeam.type =1
+-> .events[3].awayTeam.id =208824
+-> .events[3].awayTeam.teamColors.primary =#52b030
+-> .events[3].awayTeam.teamColors.secondary =#52b030
+-> .events[3].awayTeam.teamColors.text =#ffffff
+-> .events[3].homeScore.current =0
+-> .events[3].homeScore.display =0
+-> .events[3].homeScore.period1 =4
+-> .events[3].homeScore.period2 =6
+-> .events[3].homeScore.period2TieBreak =2
+-> .events[3].homeScore.point =2
+-> .events[3].awayScore.current =1
+-> .events[3].awayScore.display =1
+-> .events[3].awayScore.period1 =6
+-> .events[3].awayScore.period2 =6
+-> .events[3].awayScore.period2TieBreak =3
+-> .events[3].awayScore.point =3
Speed and number of allowed API queries per hour may be an issue. It may not work for point by point trading but swing trading could still be possible.
Also means a full rework of the Guardian BAF , unless all the rules are ported to Excel
Could also mean Tie Breaks would be tradeable
Time to get to work....
Data is there:
+-> .events[3].awayTeam.name =Andreev A.
+-> .events[3].awayTeam.slug =andreev-adrian
+-> .events[3].awayTeam.shortName =Andreev A.
+-> .events[3].awayTeam.gender =M
+-> .events[3].awayTeam.userCount =980
+-> .events[3].awayTeam.nameCode =AND
+-> .events[3].awayTeam.ranking =564
+-> .events[3].awayTeam.national =False
+-> .events[3].awayTeam.type =1
+-> .events[3].awayTeam.id =208824
+-> .events[3].awayTeam.teamColors.primary =#52b030
+-> .events[3].awayTeam.teamColors.secondary =#52b030
+-> .events[3].awayTeam.teamColors.text =#ffffff
+-> .events[3].homeScore.current =0
+-> .events[3].homeScore.display =0
+-> .events[3].homeScore.period1 =4
+-> .events[3].homeScore.period2 =6
+-> .events[3].homeScore.period2TieBreak =2
+-> .events[3].homeScore.point =2
+-> .events[3].awayScore.current =1
+-> .events[3].awayScore.display =1
+-> .events[3].awayScore.period1 =6
+-> .events[3].awayScore.period2 =6
+-> .events[3].awayScore.period2TieBreak =3
+-> .events[3].awayScore.point =3