Data · Betfair's own API
Betfair's own Exchange API, explained
Betfair operates an exchange and publishes its own Exchange API for customers Betfair accepts. That API places back and lay bets on Betfair's markets, with Betfair's keys and Betfair's liquidity.
What Betfair's Exchange API actually is
Turnkeyxgaming is not Betfair, is not affiliated with Betfair, and does not resell that API. Operators who want back and lay from us use the exchange product on the exchange data API page instead.
Betfair's Exchange API uses Betfair's own application keys, session handling and market catalogue. Prices on it are Betfair's prices. Liquidity is whatever is available on Betfair at that moment. If you want that API, you apply to Betfair, accept Betfair's terms, and build to Betfair's documentation. A vendor who claims to include Betfair's Exchange API inside an unrelated casino contract is describing a relationship this site does not have.
What Turnkeyxgaming does offer, for operators whose licence allows exchange-style betting, is the Diamond exchange. It is a back-and-lay product with cricket markets, including fancy markets, settled on the casino wallet. It is not a white-label of Betfair and it does not place bets onto Betfair's exchange.
Some feeds in the wider industry reference prices observed on large exchanges, run their own matching, or combine the two. How to ask that question of any supplier, including us, is the exchange data page. 'Exchange' is a shape of bet. It is not a synonym for Betfair's API.
Sessions, keys and whose book the bet hits
Betfair issues the application key, the session and the rate limits for its own API. An operator who wants those markets applies to Betfair and builds to Betfair's specification. A Turnkeyxgaming agreement does not include a Betfair login, and we cannot refresh one that Betfair has expired.
Back and lay bought from us is Diamond exchange: cricket markets, fancy lines included, settled on the operator wallet. Stakes stay on that product. Help-centre copy should say Diamond when it means Diamond, and Betfair when it means Betfair's Exchange API. A developer on your team may still hold a personal Betfair account for other work. That account is not our integration.
Who can grant the thing you are asking for
The two columns are different companies. A row that names Betfair is not a feature of the Diamond contract.
| You are asking for | Who can grant it | What we can do |
|---|---|---|
| A Betfair application key | Betfair, for Betfair's own customers | Nothing. We cannot issue or renew the key |
| Orders on Betfair's markets | Betfair's exchange | We do not proxy stakes onto that book |
| Back and lay from this company | A Diamond exchange agreement, where your licence allows it | Scope that product on the Diamond exchange page |
| Names in your help centre | Your editors | Use Diamond's name for our product and Betfair's name for Betfair's API |
How to choose without blurring the names
- 01
Betfair's API
Get it from Betfair if you want Betfair's markets, keys and liquidity.
- 02
Diamond exchange
Talk to us about Diamond if you want the exchange-style product this site actually sells.
- 03
Say which one
In your own help centre, do not call Diamond a Betfair feed or a Betfair reseller product.
No affiliation
Betfair and the Betfair exchange API are Betfair's. Nothing on this website is a Betfair product, a Betfair partnership or a promise of Betfair liquidity.
When Betfair's own API is the right choice, and when it is not
It is the right choice when your licence covers it, when Betfair accepts you as a customer on its own terms, and when the thing you are building genuinely needs Betfair's prices and liquidity: a trading tool, a price-comparison service, a matched-betting analysis project. In those cases apply to Betfair directly, budget for their rate limits and their specification, and treat any supplier who offers to bundle that access as a vendor describing a relationship they do not have.
It is the wrong choice when the actual requirement is exchange-style betting for your players. That is a licensed product decision, not an API key: your market may not permit it at all, and where it does, the product is an exchange contract such as the Diamond exchange, settled on your wallet, with your own help-centre naming. Between those cases sits a middle ground, reading prices for display, which is a data licence question, and the honest answer is the same as for any data supplier: ask the rights holder.
How a vendor talks about Betfair when the claim does not hold
Five phrasings that should end the conversation, or at least start a written one:
- Betfair API included in the casino contract. Access is granted by Betfair to Betfair's customers. It does not travel inside another supplier's agreement.
- We resell Betfair liquidity. Liquidity is matched on an exchange by that exchange. Reselling it means placing orders on it, which is Betfair's relationship to grant.
- A white-label Betfair exchange. Betfair does not white-label its exchange through third-party aggregators.
- Same prices, no Betfair account needed. That could be observed prices re-served, which is legitimate only as a licensed data product and should be named as one.
- Just use a personal account's key. A personal application key used for a business contradicts the key issuer's terms and ends at the worst possible time.
Three different things people call the Betfair API
| What is being asked for | What it actually is | Where it is obtained |
|---|---|---|
| Betfair's Exchange API | Betfair's own interface to Betfair's markets, for customers Betfair accepts | Betfair, by application |
| Prices that look like exchange prices | A licensed data product, observed or independently produced | A data supplier, under a data contract |
| Back and lay for your players | An exchange-style product under your licence | A supplier such as Diamond, where the licence allows it |
FAQ
Questions operators ask
Can you give us a Betfair application key?
No. Application keys, sessions and market access for Betfair's exchange API are issued by Betfair to its own customers. We cannot grant them.
Does a contract with you include Betfair's liquidity?
Betfair's liquidity stays on Betfair's exchange. Diamond matches on Diamond. This website does not join the two books.
Can your team implement Betfair's Exchange API for us?
Betfair supports that API for its customers. We discuss Diamond exchange. We do not build, host or debug Betfair's Exchange API as part of our supply.
Why does a page exist for a product you do not sell?
Because operators search for Betfair API when they mean three different things, and the fastest help is to separate them plainly. Saying what we are not is cheaper for both sides than a call that discovers it in month two.
If we get our own Betfair key, can you build the integration?
No. Our work is the products this site sells: data feeds, the sportsbook frame, Diamond, and the wallet they settle on. Betfair's API is supported by Betfair, for Betfair's customers.
Is Diamond's back and lay the same thing as Betfair?
It is the same shape of bet, not the same book. Prices, liquidity and counterparties are Diamond's. Calling one by the other's name in your help centre is the mistake this page exists to prevent.
References
Sources and further reading
Primary regulator, standards or studio documentation behind the technical and regulatory points on this page. External links open in a new tab. Links checked 2026-11-15.
- Betfair API documentation
Exchange pricing, lay liability and settlement behaviour.
developer.betfair.com
- UK Gambling Commission
Remote gambling and software technical standards.
www.gamblingcommission.gov.uk
Keep reading
Related pages
- Product · ExchangeDiamond exchangeBack and lay on cricket match odds, bookmaker and fancy markets, with lay liability reserved on the same wallet. Not the card games.Read
- Data · Exchange dataExchange dataExchange data is market state plus back and lay prices. It is not a fixed-odds feed, and it is not Betfair's Exchange API either.Read
- Product · Sports dataSports dataFixtures, pre-match and live odds, scores and results for operators who build their own sportsbook front end and settle bets themselves.Read
- Data · Cricket dataCricket dataCricket fixtures, markets, scores and results, including the ball-by-ball facts used to settle fancy and session markets correctly.Read
Get a written quote and sandbox access
Tell us your licence, target markets and products. You get the GGR rate in writing, the studio list for your markets and sandbox credentials.