Hello all,
I'm trying to develop a small app that will get the live cricket scores into a stored value in Bet Angel that can then be used for automation etc. See screenshot of a working example. I'm working on getting other data in there also (overs remaining etc). Currently restricted to single innings matches but will expand to multi innings (test matches) if this has legs.
A lot of the API's available for this have a latency or lag of around 30 seconds unless you are prepared to pay thousands.
I'm wondering if a tool like this would be valuable to anyone? Even with this delay?
MT
Live cricket scores in Guardian
-
MarketTrader
- Posts: 120
- Joined: Wed Mar 18, 2009 12:34 pm
You do not have the required permissions to view the files attached to this post.
What sort of delay are you looking at achieving? I don't see how anything with a latency of 30 would have any value.
Betfair had a cricket scoreboard API - it had some bugs, maybe they fixed them.
Don't know, don't really care.
Betfair had a cricket scoreboard API - it had some bugs, maybe they fixed them.
Don't know, don't really care.
-
MarketTrader
- Posts: 120
- Joined: Wed Mar 18, 2009 12:34 pm
That's the question really. What delay is acceptable?
Getting live scores into Bet Angel so that they can be acted upon by automation is the goal. Or would anyone find it useful to just have a live score in Guardian? I've achieved it with football but the latency is a drawback there too.
But any feed is going to have a delay as you know. So is this a pointless task?
The delay got to as low as ten seconds on the one I am using. When taking upstream node delays, caching and call rate limitations, I can't see it getting much better.
Thanks for not caring. It means a lot.
Getting live scores into Bet Angel so that they can be acted upon by automation is the goal. Or would anyone find it useful to just have a live score in Guardian? I've achieved it with football but the latency is a drawback there too.
But any feed is going to have a delay as you know. So is this a pointless task?
The delay got to as low as ten seconds on the one I am using. When taking upstream node delays, caching and call rate limitations, I can't see it getting much better.
Thanks for not caring. It means a lot.
To clarify - I wasn't caring about the Betfair bugs.
I think you are wasting time building a cricket tool with even a latency of 3 secs.
But, maybe it has other side benefits.
Being live, or acting on live feeds (within 4 secs of live) is all that matters for 99% of cricket markets (IMHO) - but everyone needs
to assess these things for themselves.
GL
I think you are wasting time building a cricket tool with even a latency of 3 secs.
But, maybe it has other side benefits.
Being live, or acting on live feeds (within 4 secs of live) is all that matters for 99% of cricket markets (IMHO) - but everyone needs
to assess these things for themselves.
GL