Hi
I know the new API doesn't restrict in terms of the number of data requests anymore...
However, if I were to run two instances of Betangel on the same market (200ms Refresh) would this cause a "Too_Much_Data error"on the API? Would the Betfair BDP team see this as an abuse in some way?
Thanks in advance
regards
Peter
Market Data Requests..
I think the "too much data error" you mention only applies when requesting too many markets in one go. (In the previous API you could only query one market in one request, whereas API-NG allows you to query multiple markets in one request up to a certain limit and hence the error). I'm obviously not aware of how BetAngel makes use of this multiple market querying feature, if at all.
In terms of the frequency of the requests, I do recall someone here mentioning that Betfair ask you not to request a specific market more than 10 times a second? Can't remember exactly, or where that information came from.
I myself have been requesting data at 10 times a second without any problems yet. I don't believe there is currently any official rule about how frequently you can refresh or how Betfair would respond to anything over the limit.
Anyone else have any more info? If no one knows, perhaps one of us should contact BDP to get an official stance on the matter?
In terms of the frequency of the requests, I do recall someone here mentioning that Betfair ask you not to request a specific market more than 10 times a second? Can't remember exactly, or where that information came from.
I myself have been requesting data at 10 times a second without any problems yet. I don't believe there is currently any official rule about how frequently you can refresh or how Betfair would respond to anything over the limit.
Anyone else have any more info? If no one knows, perhaps one of us should contact BDP to get an official stance on the matter?
I was just browsing the BDP forum, and came across a post about a different error, TOO_MANY_REQUESTS, which is probably more related to what you're talking about.
http://forum.bdp.betfair.com/showthread.php?t=2838
Apparently you can't have more than 3 concurrent requests for listMarketBook, listCurrentOrders and listMarketProfitAndLoss.
Now of course I don't know what requests BetAngel uses behind the scenes, but it's likely that it uses a combination of these. So there probably is a very small probability that two instances of BetAngel might collide and fire off 4 concurrent requests using the calls above and causing one of them to fail.
The documentation doesn't mention any sort of blacklisting should you be caught by that error though.
http://forum.bdp.betfair.com/showthread.php?t=2838
Apparently you can't have more than 3 concurrent requests for listMarketBook, listCurrentOrders and listMarketProfitAndLoss.
Now of course I don't know what requests BetAngel uses behind the scenes, but it's likely that it uses a combination of these. So there probably is a very small probability that two instances of BetAngel might collide and fire off 4 concurrent requests using the calls above and causing one of them to fail.
The documentation doesn't mention any sort of blacklisting should you be caught by that error though.
-
Wainwright
- Posts: 108
- Joined: Mon Jan 23, 2012 1:10 pm
The documentation states;
"Should" rather than "must".
- I try to keep to that limit though.
https://api.developer.betfair.com/servi ... MarketBookCalls to listMarketBook should be made up to a maximum of 5 times per second to a single marketId.
"Should" rather than "must".
- I try to keep to that limit though.
To be honest, I think as long as you're contributing to the exchange, i.e. adding liquidity or genuinely trying to get bets matched, which I'm sure you are, then they shouldn't really have any problems with it.
The concern I have is that by not having any strict rules they are not discouraging people from making masses of requests and are creating future scalability problems. I would much prefer them to put in restrictions for everyone now rather than wait until they're reaching breaking point and doing it.
The concern I have is that by not having any strict rules they are not discouraging people from making masses of requests and are creating future scalability problems. I would much prefer them to put in restrictions for everyone now rather than wait until they're reaching breaking point and doing it.