For teams building odds comparison, tipping, analytics and trading products. This page sets out which licence fits what you are building, what the team plans carry, where the data comes from, how it is secured and supported, and how a commercial enquiry runs.
The licence follows from the plan, and it is the question that decides the plan more often than volume does. Find the row that describes your product.
Plus and Business are different permissions, not different sizes of the same one. Plus lets you SHOW our prices in one product, and carries the commercial permission that product needs. Business lets you USE the data anywhere in your business, whether or not a price is ever displayed.
What these licences do and do not cover, from section 8.2:
These licences are ours to give over our compiled feed and our derived works. They are not a warranty about the underlying bookmakers' own terms, about third-party data rights, or about the gambling, advertising and consumer law that applies where you and your users are located. You remain responsible for your own compliance in your own jurisdiction.
If your use does not fit these shapes, say so in the enquiry. Section 8.1 again: we will put something in writing rather than leave you guessing
.
The figures below are the limits the API itself enforces. Prices are in Australian dollars a month. The full grid, including the personal plans, is on the pricing page.
| Plan | Price | Credits / month | Rate limit | API keys | Licence | How to buy |
|---|---|---|---|---|---|---|
| Plus | A$49 | 140,000 | 500 requests/minute | 1 | Display with attribution | Card checkout |
| Business | A$99 | 300,000 | 750 requests/minute | 3 | Commercial use | Card checkout |
| Platform | A$199 | 1.5M | 1,000 requests/minute | 5 | Redistribution | Through us |
| Scale | A$249 | 5M | 2,000 requests/minute | 10 | Commercial use | Through us |
On plans with more than one API key, the keys share one credit pool. Business and Platform can switch on credit overage (Terms 6.6). Platform and Scale are sold through us, and Platform can start as a 30-day pilot.
What a price in the feed is, from section 9.1 of the Terms:
A price in our Data is our observation of the price a bookmaker was displaying at the time stamped on that quote.
Results and racing records, from section 9.2:
Results, dividends, fields, scratchings, acceptances and form are compiled from public racing records and bookmaker results feeds.
And from section 8.6: Some sources we collect are withheld from customer responses where we do not hold the rights to pass them on
.
What is served is measured in public, and section 9.3 makes that measurement the standard: The coverage report and the data-quality page measure what is being served now, and that measurement, rather than any list elsewhere, is what we hold ourselves to.
/uptime.json: availability as measured from outside our servers.From section 7 of the Privacy Policy:
All traffic to the website and the API is encrypted in transit. Passwords are stored as bcrypt hashes and API keys as cryptographic hashes; neither can be read back. Sensitive actions in the console, such as revealing a key or opening billing, ask you to confirm your password or to use a fresh sign-in. You can end every session on your account from the console, and we email you whenever your password is set or changed. Paid plans can restrict a key to listed IP addresses. Access to production systems is limited to the operator, and the database is backed up nightly with copies kept offsite. Payment data is handled entirely by Stripe.
on infrastructure in Sydney, Australia(Privacy Policy section 5, which lists every provider and where it is).
After a rotation the previous key keeps working for 24 hours so that running systems can be updated, unless you choose to revoke it immediately(Terms 4.3).
Your card details are entered with and held by Stripe; we never see or store them.(Terms 6.1)
We do not receive the personal information of your own users when you build a product on the API, except as described in 2.5 for visitors to embedded widgets.(Privacy Policy section 2)
If you have a security questionnaire or a procurement requirement, attach it to the enquiry and we will answer what we can in writing.
Every plan includes email support during Australian business hours. Business plans are answered within one business day (AEST), and Platform plans within four business hours on a direct channel, with a monthly call, as published on the pricing page; Scale includes dedicated support, which is the same target as Platform: within four business hours on a direct channel, with a monthly call. A response target is a commitment to reply, not a guarantee that every problem can be resolved in that time.
Section 9.7: Business and Platform plans are entitled to at least 30 days' notice of a breaking change.
New endpoints and fields arrive continually, and additions do not change existing behaviour
. Retired endpoints answer HTTP 410 and are not charged.
Section 9.6: the self-serve plans carry no uptime guarantee
. Availability is measured from outside our servers and published on /status, with its incident history, and in /uptime.json, so you can read the record without asking us. Design for retries and a fallback, as the Terms advise.
Where your plan includes them, webhooks are signed. Section 9.8: Delivery is best-effort
, so treat them as a complement to polling.
By card through Stripe, monthly or annually; receipts and tax invoices come from Stripe (Terms 6.1). Section 6.4: Switching between monthly and annual billing is done by hand: email us and we will arrange it at your next renewal.
You can also start on a free key today and upgrade the same key later; nothing you build has to change.