Betfair API pricing often confuses teams, because there is no per-call price list to compare. Instead, the cost of the Betfair API is a mix of a free delayed key, a one-off fee for the live key, commercial licensing agreed with Betfair, commission on winnings and, if you poll too hard, data request charges. Add your own build cost and the real budget only becomes clear once every piece is on the table.
This guide breaks down each of those costs, explains the licensing and eligibility rules behind them, and shows how the delayed and live keys, the REST API and the Stream API affect what you pay. If you are ready to build, our guide to Betfair API integration for real-time sportsbooks covers the implementation side.
Betfair API Pricing: What You Actually Pay
There is no per-call price list for the Betfair API, so the total depends on which keys, licences and usage patterns apply to you. Here is how each piece of Betfair API pricing fits together:
| Cost item | What it is | Things to know |
|---|---|---|
| Delayed application key | Free key for development and testing | Returns delayed prices and runs against the live exchange, not a sandbox |
| Live application key | One-off activation fee for real-time data and betting | Commonly cited at around £299 for personal use; confirm the current fee with Betfair |
| Commercial or vendor licence | Terms agreed directly with Betfair | Required for any commercial use of the API or its data |
| Exchange commission | Charged on net winnings in a market | Depends on the market base rate and your discount rate |
| Data request charges | Applied when weighted data usage is high compared with betting activity | Inefficient polling can become an actual cost |
| Historic data packages | Paid downloads of past market data | Useful for back-testing and analysis |
| Your own build cost | Development, infrastructure, security and compliance | Usually the largest line item |
Treat these figures as indicative. Fees and terms change, so always confirm them in Betfair’s documentation or with Betfair Developer Support before you finalise a budget.
How to keep Betfair API pricing under control
- Stream instead of polling. Use the Exchange Stream API for anything that updates often, and keep REST calls for discovery, account data and order placement.
- Request only what you need. Ask for the price data your screen actually displays. Market data requests are weighted, and a single request has a weighting cap, so lean requests are both faster and cheaper.
- Batch your orders. Group instructions where the API allows it instead of firing them one by one.
- Cache static data. Event lists and market catalogues change slowly, so refresh them on a schedule rather than on every page view.
- Log your usage. A simple dashboard of requests per minute will expose a runaway polling loop long before it shows up as a charge.
Betfair API Licensing and Eligibility: Read This Before You Budget
Betfair’s documentation is clear that any commercial use of the API or its data must be approved by Betfair, and that unauthorised commercial usage is identified and blocked. The delayed key is perfect for testing and simulation, but it is not a substitute for a licence.
Betfair describes several commercial licence types, roughly along these lines:
- Software vendor licence – for companies building software that other people will use with the Betfair API.
- Odds publisher licence – for affiliates who want to publish Betfair odds.
- Betting operator licence – for licensed operators who want to use exchange data.
Eligibility also depends on geography. Betfair publishes a list of countries from which it does not accept licence applications, and at the time of writing that list includes India, Bangladesh, Sri Lanka and the UAE. On top of that, betting regulation differs by country and, in the USA, by state. Before you build anything on the Betfair API, check whether you and your end client can actually obtain access in your target market, ideally before you sign contracts or write production code.
What Is the Betfair API? A Quick Primer
The Betfair API (also known as API-NG) is the programmatic doorway into the Betfair Exchange. Instead of clicking through the website, your software can browse markets, read live prices, place and manage bets, and check account state. In practice, the Betfair API is a family of interfaces rather than a single endpoint:
- Betting API – market catalogues, market books, prices, traded volume and order operations such as placing, replacing and cancelling bets.
- Accounts API – funds, statements and the calls used to create your application keys.
- Heartbeat API – a safety timer that lets unmatched bets be cancelled if your client stops communicating.
- Exchange Stream API – a push channel that delivers market and order changes with low latency.
- Historic Data – purchasable archives of past market data for research and back-testing.
An exchange behaves differently from a bookmaker. Customers offer back and lay prices to each other, so the Betfair API exposes an order book instead of a single line set by a trader. That is exactly why developers value it: the prices reflect real money from real participants, not a bookmaker’s margin.
Getting Started With the Betfair API: Keys, Login and Your First Call
- Create your account and application keys. Use the Accounts API demo tool and the createDeveloperAppKeys operation. You receive two keys, a delayed key and a live key, and the live key stays inactive until Betfair approves it.
- Set up non-interactive login. For bots and backend services, Betfair supports certificate-based login with a self-signed certificate, your credentials and the application key sent in the X-Application header. The result is a session token you attach to every later call.
- Make your first call. List the available sports, then work down to events and markets to see how the Betfair API structures its data.
- Test on the delayed key. Finish your testing before you ask for anything more, and remember that the delayed key returns delayed prices.
- Apply for live access. Follow Betfair’s process for activating the live key and, where relevant, a commercial licence, then move on to the Stream API if you need real-time updates.
Here is a minimal Python example of the first two calls to the Betfair API. Keep real credentials in a secrets manager, never in source code:
import requests
APP_KEY = 'YOUR_APP_KEY'
# 1. Non-interactive login with your self-signed certificate
login = requests.post(
'https://identitysso-cert.betfair.com/api/certlogin',
data={'username': 'YOUR_USERNAME', 'password': 'YOUR_PASSWORD'},
cert=('client-2048.crt', 'client-2048.key'),
headers={'X-Application': APP_KEY},
)
session_token = login.json()['sessionToken']
# 2. First data call: list the available sports (event types)
headers = {
'X-Application': APP_KEY,
'X-Authentication': session_token,
'Content-Type': 'application/json',
}
sports = requests.post(
'https://api.betfair.com/exchange/betting/rest/v1.0/listEventTypes/',
json={'filter': {}},
headers=headers,
)
print(sports.json())REST vs Stream: Which Part of the Betfair API Costs Less to Run?
| REST / JSON-RPC requests | Exchange Stream API | |
|---|---|---|
| Best for | Market discovery, account calls, order placement | Live prices, in-play dashboards, order tracking |
| How data arrives | You ask, Betfair answers | Betfair pushes changes after you subscribe |
| Latency | Depends on your polling interval | Low latency, delta-based updates |
| Data weight | Easy to overspend | Efficient for frequent updates |
| Access | Delayed or live key | Live key, subject to Betfair approval |
With the stream, you open a secure socket, authenticate with your application key and session token, and send a market subscription with the filter you need. Betfair then sends an initial snapshot followed by change messages. A heartbeat keeps the connection healthy, and a conflation setting lets you slow updates down when your screen cannot use every tick. Because the stream is a raw SSL socket rather than WebSocket, browsers cannot connect to it directly, so most teams consume it on a backend and pass updates on to the front end.
Common Betfair API Mistakes to Avoid
Most problems with the Betfair API come from the same handful of shortcuts:
- Polling everything. Looping over market-book requests for dozens of markets is slow, expensive and fragile. Move live data to the stream.
- Ignoring session expiry. Session tokens do not live forever. Build keep-alive and re-login logic from the start.
- Hard-coding secrets. Certificates, passwords and application keys belong in a secrets manager with rotation, not in a repository.
- Forgetting order states. Unmatched, partially matched and lapsed orders all need handling, otherwise your exposure numbers drift from reality.
- Underestimating in-play behaviour. Markets suspend, prices jump and bet delays apply. Your interface and your risk engine should expect all three.
- Skipping the licence conversation. Building first and asking about commercial approval later is the most expensive mistake of all.
Conclusion
Betfair API pricing is less about a monthly fee and more about three things: the one-off live key, commercial licensing and how efficiently you use data. Start on the free delayed key, confirm your eligibility and licence route with Betfair early, and lean on the Stream API so heavy polling never becomes a cost.
If you want hands-on help with the Betfair API, our Betfair API experts are ready to talk through your product. To see how it comes together in a live product, read our guide to Betfair API integration for real-time sportsbooks.
FAQ’s
1. What is the Betfair API used for?
The Betfair API lets software connect to the Betfair Exchange to read markets and prices, place and manage bets, check account data and receive live updates through the Stream API. It powers dashboards, trading tools, automation and analytics products.
2. Is the Betfair API free?
The delayed application key is free for development and testing. Real-time data and live betting need a live application key, which carries a one-off activation fee, and commercial use needs approval or a licence from Betfair. Commission and data request charges can also apply.
3. What are Betfair API data request charges?
Betfair may charge accounts whose weighted API data usage is high compared with their betting activity. Using the Stream API instead of heavy polling, and requesting only the price data you need, helps keep these charges away.
4. How much does it cost to build on the Betfair API?
A Betfair API MVP needs a minimum of roughly $15,000 to $25,000, while an enterprise-level module runs from $75,000 to $120,000. The final figure depends on scope, and Betfair API pricing (keys, licences, commission and data charges) is separate.
5. What is the difference between the delayed and live Betfair API keys?
The delayed key is free and returns delayed prices, so it suits development and testing, but it still runs against the live exchange rather than a sandbox. The live key stays inactive until Betfair approves it, and it is what you need for real-time prices, live betting and Stream API access.
6. Can anyone get a commercial Betfair API licence?
No. Betfair does not accept licence applications from certain countries, and betting laws differ across markets. Check current eligibility with Betfair and take local legal advice before you build.
7. Is the Betfair API good for real-time betting apps?
Yes, when you use the Exchange Stream API for live data. Polling alone is rarely enough for in-play products.
8. How does login work for automated systems?
Betfair supports a non-interactive login that uses a self-signed certificate, your account credentials and an application key in the X-Application header. The call returns a session token that you send with every later request.
Leave a comment