In their own words. Every quote here arrived by email from someone building on the API, is published with their permission, and is credited the way they asked.
The counter on the homepage is a live count of real external accounts and the requests they have made, refreshed every few minutes and never typed in by hand. It says how many people build on the data; the quotes here say why. Names appear exactly as the customer asked. Some prefer an initial to a surname, because the bookmakers they price against read this site too.
We were a little unsure about the reliability and latency of the data at first, as the service we used before had issues there. It has ticked all our boxes: accuracy and speed are king for us, and so far it has looked good on our end. The place prices have been a nice addition, as our previous source only carried win prices, and the results have been a good backup check on racing data we source elsewhere. We'd recommend it for sure; it's been reliable and affordable for us so far.
Named in this quote/v1/racing/results
I expected to still be stitching sources together, because the big thoroughbred providers leave greyhounds and harness bare. Instead the greyhound coverage is genuinely deep: form, results, closing lines and best odds all behind the one key, with harness results and closing lines alongside, and every call metered so I can run it automated without surprises. It's what let me build a proper model for those codes and measure it honestly against the closing line.
Named in this quote/v1/racing/greyhounds/form/v1/racing/results/v1/racing/closing-lines/v1/racing/best-odds
I wasn't really sceptical going in, and an early credits mix-up didn't bother me, as it was fixed straight away. The data is clean and consistent, and it held up from testing into live without changes on my side. The live prices are the most useful part: they power the price column on every race, and best odds and next-to-go give me what I need in two calls per poll. It's been consistent too; it hasn't failed on me yet that I know of. It also lets me show market moves, the firmers and drifters, across bookmakers, and because the live prices are free for every user on the site, they help with sign-ups. I'd recommend it to anyone building a racing tool in Australia who needs reliable live bookmaker prices without scraping.
Named in this quote/v1/racing/best-odds/v1/racing/next-to-go
The big issue for me with price providers is bookie availability and then stale prices. I had a look at PuntersEdge and found it was close to what I needed, so I contacted Hamish, we went through things and he quickly added the functionality. I'm now finding that the data I download through the day is available, up to date and accurate, which is exactly what I need. It's all been pretty useful, but being able to use webhooks at a reasonable price has enabled functionality that I didn't have before. I've also now got access to sports pricing, which I didn't have with other providers, so I'm looking to add that to my portfolio. I would definitely recommend it: a fast and reliable API across a good range of racing and sports, at what I think is the correct price point, topped off with quick support when needed. PuntersEdge is a one-stop shop for sports and racing pricing that allows punters to up their game by having access to a wide range of prices and tools at a decent price. I've used all of the others and PuntersEdge really has hit a sweet spot.
Named in this quote/v1/webhooks
Going in, my main doubt was whether a relatively new API would have enough coverage and consistency for what I was building, particularly across full Australian race cards on busy Saturdays, and how quickly genuine gaps would be dealt with once they showed up in real use. The breadth was better than I expected. Once I was using the endpoints together there was enough to build around rather than just use it as an odds feed, and while there have been gaps and edge cases, they have generally been visible rather than hidden. The most useful part has been having acceptances, results, horse data and market data through the one API; tying those together has been worth more to me than any single endpoint. The biggest benefit beyond that has been the turnaround. The acceptance-card work, a scratching issue and a few identity problems we found were investigated and addressed rather than brushed off, and when something upstream isn't working properly we are told, rather than handed data that looks complete when it isn't. I have probably pushed it harder than the average user, so I have seen both the good parts and the things that still need work. For someone building their own racing analysis or automation rather than looking for a finished tipping product, I would recommend it: it gives you a broad set of building blocks and the development has been very responsive to real-world use.
Named in this quote/v1/racing/acceptances/v1/racing/results
I’m testing the API alongside our existing source rather than replacing anything. My main concern was whether the API data would reconcile reliably enough with the other racing data First4 Pro uses — runner identity and matching accuracy particularly, because a silent mismatch could contaminate the analysis. The integration has been straightforward and the matching has been very good: in one validation run First4 Pro matched all 41 active runners across five races with no ambiguous matches, and when we did find an issue with missing runner references, the diagnostics gave us enough information to identify it precisely. Stable race and runner identifiers, together with market data, give First4 Pro a much stronger provenance trail and let me verify exactly which provider record was used in the analysis. What I value most is that I’m able to treat PuntersEdge as a factual data source rather than a tipster: First4 Pro does its own evidence assessment and probability work, so reliable underlying data and traceable identifiers are more important to me than somebody else’s selections. First4 Pro is still in prospective validation.
My main question was whether the data would have enough depth, granularity and stable identifiers to build a proper quantitative racing and backtesting platform around it, rather than simply being another odds and results feed. It's been much more comprehensive than I initially expected. The timestamped bookmaker price movements, stable race IDs, results, closing lines and now runner_ref give me a very clean structure for connecting market behaviour to individual horses and races. The permanent price-path history is probably the standout: being able to follow price changes by bookmaker and then link them through runner_ref to results, closing lines and horse form is particularly useful for the type of quantitative research I'm building. The responsiveness has been exceptional. I've raised questions and requirements around stable runner identity, bulk exports and Parquet, and Hamish has either explained the existing capability in detail or implemented improvements very quickly. The transparency around nulls and edge cases has also made integration much easier. The biggest positive for me has been the willingness to explain what the data can and can't do. Things like historical coverage, point-in-time limitations and the Betfair licensing restriction have been explained clearly rather than glossed over, and that matters when you're trying to build and validate models properly. For someone building their own racing analytics, modelling or backtesting platform, I think it provides a very strong data foundation without having to piece together market history, results and horse identity from a number of unrelated sources.
Named in this quote/v1/racing/price-paths/v1/racing/results/v1/racing/closing-lines/v1/racing/horses/form
Before I signed up I was skeptical the odds would be refreshed often enough to be useful. I discovered they were updated well within the timeframes I needed, and I'm refreshing the markets multiple times per minute! It was so quick and easy to get started and I had immediate visibility across all the bookmakers I cared about. What I've appreciated is how simple it's been to upgrade as my usage has grown. The system has also been very reliable, and they've kept adding features I can use. Trying to build and run something like this myself would have taken months of effort and been a distraction from the actual systems I want to build. The few times I have had a question, customer support has sorted me out quickly.
RaceVision uses PuntersEdge data across its Australian racing platform, including automated race results and historical market data as we develop our closing-line analysis and model evaluation capabilities.
Named in this quote/v1/racing/results
90+ paying customers build on the API. These are the three patterns in what paying accounts call, most common first. Nobody is named and nothing here is a quote: they are endpoint families, and most accounts follow more than one.
Poll the next races across every Australian bookmaker, show the best price per runner, and fetch only what moved since the last poll instead of the whole card. Tipping sites, odds widgets and private dashboards all start here.
/v1/racing/next-to-go/v1/racing/best-odds/v1/racing/changes/v1/racing/events
Pull official results to settle tips and bet trackers automatically, read acceptances and track conditions before the card opens, and feed horse and greyhound form plus jockey and trainer stats into ratings.
/v1/racing/results/v1/racing/acceptances/v1/racing/horses/form/v1/racing/jockeys/stats
Replay how a market moved before the jump, compare the price you took with the close at each bookmaker, and backtest a model against what was actually on offer, not a single reference price.
/v1/racing/price-history/v1/racing/closing-lines/v1/racing/price-paths/v1/racing/movers
If you'd like to be here, reply to any email from us with a few sentences on what you're doing and how you'd like to be credited. Initial, full name, company, link, or none of those: your call, and we print it the way you send it. Get a free key if you haven't started yet, or read the devlog to see what customers have asked for and what shipped.