Tabcorp is an Australian Wagering Company that offers real-time horse racing APIs: https://studio.tab.com.au/
Others are a little less public and you need to sign up with an account and prove you are a syndicate. Hong Kong Jockey Club, UniBet, Amtote.
I don't normally talk about this history as I was active in this industry until four years ago. There are however people who have come out in public:
Bill Benter: https://www.bloomberg.com/news/features/2018-05-03/the-gambl...
Jelko: https://www.smh.com.au/national/meet-the-joker-the-australia...
Most of the other families and players are extremely private or are of Eastern European I wont talk about them publicly.
This is a list of common bet types that are targets for these types of players: - Trifecta - Big Six - Quadrella - First 4
Here is a blog on working the combinations of the Big Six: https://practicalpunting.com.au/pp-online/a-z-of-betting/exo...
What are you up to now Shaun? Are you still in Hobart?
Tabcorps TABStudio - http://studio.tab.com.au/ (You need to register as a tabcorp customer but it's "free"). Its basically a JSON REST API
NZ TAB have their batch mode, at filebet.tab.co.nz, which is nothing more than a file upload system.
The ATG, and the other Scandinavian totes provide coupon upload systems (where you generate a coupon file with your selections in it, using third party software), but if you win they will end up banning you.
Most providers keep their APIs hidden or require signing NDAs or other types of contracts, I'm referring to companies like Amtote, Churchill Downs, PMU, BetFred, PGI, LeTurf etc
Usually they're quite surprised when you contact them about doing "integration work", a lot of the APIs are designed for retailer shops to integrate with. For example, I've done some integration work with BetFred, where my client never wants to cancel a bet (placed at the last possible moment), however in order to pass their integration tests, I have to fully support cancelling a wager, just like any retail shop would.
On a side note, I have used (at least one of) the APIs shaunray was referring to that he had worked on.
technologically the book is a couple of decades out of date, but it's probably worth a read.