Race Status API : Is it to delayed to be useful?

[Escapee]

Hi There,

I've just started looking at "Race Status API" for Greyhound racing and I found a delay of 1 or 2 minutes between an event happening ( such as 'APPROACHING' or 'GOINGINTRAPS' ) and it being reported in the "Race Status API".

This delay means that it can not be used to place bets as they go into the traps as generally the race is already 'off' by the time the api reports it as 'GOINGINTRAPS'


Is this delay because the operators don't put in the status change in a timely manner?

Or is there a secret hidden parameter to get the status without delay?

Does anyone else use the "Race Status API" ?

All replies welcome.

[Mr Magoo]

I just checked with the 16:37 race and I saw the status change from PARADING to APPROACHING -> GOINGINTRAPS before the race started.

Perhaps you are using a delayed API key?

[Escapee]

Hi Mr Magoo,

I'm definitely using the real time app key

I just did another test on the Hove 16:47 and here is the output

"raceId":"28002316.1647","lastUpdated":"2016-11-04T16:43:49.882Z","raceStatus":"PARADING"
"raceId":"28002316.1647","lastUpdated":"2016-11-04T16:46:19.121Z","raceStatus":"APPROACHING"
"raceId":"28002316.1647","lastUpdated":"2016-11-04T16:47:19.489Z","raceStatus":"GOINGINTRAPS"
raceId":"28002316.1647","lastUpdated":"2016-11-04T16:47:49.110Z","raceStatus":"OFF"

The actual race suspend time was 16:47:31 so in this case there was 12 seconds between going in traps and 'OFF'

I was listening to the race on the BF radio commentary and they were saying that they were loading the traps about 1 minute before the race api status changed to 'GOINGINTRAPS'

around midday when I first looked at it, there were many instances of the race starting whilst the status was 'APPROACHING'

[Mr Magoo]

Unfortunately I don't have a record of past races compared with the raceStatus times, so I can't offer much more than than me just watching the current races. The race status for the 16:47 look 'good enough' to my eyes, i.e. if you get a heads-up about GOINGINTRAPS then you know that the race will start very soon. As long as you see this status before the market suspends, I'd count that as good enough.

Watching the 17:17 race now, the GOINGINTRAPS apeared around 17:16:49, race off around 17:17:18. I see your point that the GOINGINTRAPS is likely delayed (the loading process seems very short) but it seems good enough for any last minute betting purposes?

[Mr Magoo]

Hmm... the 17:22 just went from APPROACHING to market suspended. Then HARERUNNING. So no GOINGINTRAPS at all there!

[Escapee]

17:22 at hove was still 'APPROACHING' when race was suspended at 17:24:20

04T17:22:20.249Z","raceStatus":"APPROACHING","resp onseCode":"OK"}],"id":1}

Shame as it could be really useful if it was more reliable and less delayed

[altisw]

Hello,
Just firing (although this is ~6 years old post): someone can help with a code sample?
I'm using Java, and the following throws an error:

{"jsonrpc": "2.0", "method": "ScoresAPING/v1.0/listRaceDetails", "params": { "meetingIds": [31485333]}}

Thanks in advance