Race Status - listRaceDetails Changes since 31/03 ?

[jrvoice]

Hello!

I use the Betfair API with my own Python engine to get the race status as a trigger, so GOINGBEHIND etc is my trigger to place a bet.

I've had some trouble since yesterday where all races were stuck at DORMANT no matter what was going on, including while the market should have been in-play (OFF) etc.
This morning all the race status is showing is "NO_LIVE_DATA_AVAILABLE" which is weird; I've cross-checked my market ID's and raceID's and even built a standalone debug script to prove its not my handling of it!

2026-04-01 09:39:24 UTC locked marketId=1.256051607 Scores_raceId=35432485.1320 marketStartTime='2026-04-01T13:20:00.000Z'
2026-04-01 09:39:24 UTC raceId='35432485.1320' raceStatus=None responseCode='NO_LIVE_DATA_AVAILABLE' marketId=1.256051607

Given there is no-one saying anything about it, is it my account that has got screwed up somehow - or is this a generic thing?

I've seen on the Betfair Developer website that some of the docs were updated 4 days ago *gulp* but can't find anything definitive relating to listRaceDetails having changed.

Any pointers gratefully received! Everything else looks to be fine.

Many thanks,
Jon

[ynotrek78]

Hi Jon,
I have noticed since the clocks changed there is a discrepancy between race times in the URL and the real race time...could that explain it?

[jamesedwards]

Didn't notice anything yesterday, but today all horse race statuses in Guardian are blank. Greyhounds are still working normally.

z098.jpg

[sniffer66]

I'm seeing some odd stuff in my code. This only loads GB\IRE markets and these have all closed and settled this morning. Never see these until normal race settlement usually, unless a meeting has been called off. Something odd going on

Screenshot 2026-04-01 135417.jpg

[Euler]

We're having a look at this at the moment. We have reported to Betfair.

[Facedcomic]

For me it started yesterday afternoon and I thought it was me until today. I'm only horse racing. Just returning no values today across the board.

[jrvoice]

For me it started yesterday afternoon and I thought it was me until today. I'm only horse racing. Just returning no values today across the board.

Thanks everyone - I'm happy its not me now!

[Euler]

Betfair are investigating and looking for a resolution.

[Facedcomic]

Returning DORMANT values across the board. Promising.

[LinusP]

From Neil

This issue has now been fixed.

It was the result of us losing the connection to the feed that supplies this data and this has now been reestablished.

Apologies!

[mariolaht]

Hello!

I use the Betfair API with my own Python engine to get the race status as a trigger, so GOINGBEHIND etc is my trigger to place a bet.

I've had some trouble since yesterday where all races were stuck at DORMANT no matter what was going on, including while the market should have been in-play (OFF) etc.
This morning all the race status is showing is "NO_LIVE_DATA_AVAILABLE" which is weird; I've cross-checked my market ID's and raceID's and even built a standalone debug script to prove its not my handling of it!

2026-04-01 09:39:24 UTC locked marketId=1.256051607 Scores_raceId=35432485.1320 marketStartTime='2026-04-01T13:20:00.000Z'
2026-04-01 09:39:24 UTC raceId='35432485.1320' raceStatus=None responseCode='NO_LIVE_DATA_AVAILABLE' marketId=1.256051607

Given there is no-one saying anything about it, is it my account that has got screwed up somehow - or is this a generic thing?

I've seen on the Betfair Developer website that some of the docs were updated 4 days ago *gulp* but can't find anything definitive relating to listRaceDetails having changed.

Any pointers gratefully received! Everything else looks to be fine.

Many thanks,
Jon

I'm seeing similar reports, so it may not be an issue with your account. If your market IDs and race IDs are correct and everything worked before, it's possible there's a temporary problem or backend change affecting listRaceDetails. I'd keep an eye on the developer forum and status updates, and hopefully Betfair can confirm whether this is a service issue or an API change.