bet365 has no public API, so every team building on its prices hits the same wall. Here's the honest landscape, and the option that gets you bet365 odds already matched against exchange lay prices.
bet365 has no public or self-serve API. There is no developer portal, no documented endpoints, and no key you can sign up for. So every team that wants bet365 prices in a product hits the same wall, then picks one of a small number of realistic options. This guide walks through them honestly, and explains why the prices alone are only half of what you actually need.
No. Unlike Betfair, which publishes a developer API, bet365 does not offer a public, self-serve or partner-level API for odds. Searching for one is how most builders arrive here: the consensus answer across developer forums and vendor pages is the same, and it has not changed. If you need bet365 odds, you cannot request them from bet365 as a developer.
That single fact shapes the whole market. Because there is no official feed, anyone offering bet365 data is sourcing it themselves, and the quality of that sourcing, not a published spec, is what you are really buying.
The phrase usually means one of three different things, and it helps to separate them before you choose an approach:
Most products that advertise a "bet365 API" deliver the first kind. The gap between raw prices and matched, maintained data is where almost all the real engineering cost lives.
There are two routes: build your own collection, or license a feed that already includes bet365. They differ enormously in cost and reliability.
Building your own means committing to ongoing collection and maintenance for a book that is widely regarded as the hardest to cover well. Bookmaker pages change, markets are deep and numerous, and a pipeline that worked last month can quietly go stale. The prices are the easy 20%. Keeping them accurate, complete and fresh is the other 80%, and it never finishes.
Licensing a feed flips the maths. You get bet365 as a normal part of the dataset, kept current by a team whose only job is keeping it current, with the prices already matched against exchange lay odds. You spend your time on your product instead of on a collection arms race. That is the route we built OddsRelay to be.
Raw bet365 odds are not directly usable for matched betting or arbitrage. To find a qualifying bet or a sure bet you need the back price and the current exchange lay price for the same selection, the implied position between them, and enough liquidity for the lay to be real. Matching is the step that turns a price into an opportunity.
A matched feed does that step before you receive the data. Each row carries the bet365 back price, the paired exchange lay price, a rating, and the qualifying loss, so your oddsmatcher or scanner renders results on day one instead of after months of building a matcher. Here is the shape of a single matched row (illustrative, not live data):
{
"event": "Arsenal vs Chelsea",
"market": "match_odds",
"selection": "Arsenal",
"back": { "bookmaker": "bet365", "odds": 2.10 },
"lay": { "exchange": "betfair", "odds": 2.14, "liquidity": 1840 },
"rating": 98.1,
"qualifying_loss": -0.12
// ... region, feed_type and freshness fields elided
}The field that a raw API can't give you is the lay block paired to the bet365 back price, with rating and qualifying_loss computed. That pairing is the product. See the full envelope in the API docs, and check what is live right now on the coverage dashboard.
Be wary of anyone promising "real-time" bet365 odds without qualification. Our honest posture is pre-match polling on roughly a few-second cycle, which suits pre-match matched betting and pre-match arbitrage well. We publish freshness, uptime and latency on the dashboard rather than asking you to take a number on trust. If a vendor won't show you their reliability, treat the live-streaming claims with caution.
Three kinds of product lean on bet365 prices, and each wants the matched version rather than the raw one:
| Product | What it needs from bet365 data | Why matched matters |
|---|---|---|
| Matched-betting / oddsmatcher | bet365 back price paired with exchange lay | The qualifying bet *is* the back/lay pair; raw prices can't show it |
| Arbitrage scanner | bet365 price vs the best opposing price | An arb is a relationship between prices, not a single number |
| Odds comparison | bet365 alongside other books, consistently | Coverage gaps and stale prices break trust with users |
If you are building any of these, the deciding question is not "can I get a bet365 number" but "can I get bet365, matched against the exchanges, kept reliable, without owning the collection problem." For more on the build-versus-buy maths, see why teams stop scraping and buy a feed, and for the next step in this cluster, how to get bet365 odds.
bet365 has no public API, so you either build and maintain your own collection for the hardest book to cover, or you license a feed that includes bet365 already matched against exchange lay prices. For most teams the second option is faster to ship and cheaper to run. OddsRelay delivers exactly that, and it powers a leading UK matched-betting platform today. You can see the coverage live before you commit.
Written by
Founder, OddsRelay
James is the founder of OddsRelay — the odds-data feed behind matched betting, arbitrage and odds-comparison products: 60+ UK bookmakers with bet365 included, matched against exchange lay prices and delivered as one clean, documented API. He writes here about how that data layer actually behaves — coverage, matching, freshness and the trade-offs — from the side that builds and runs it. The same feed powers a leading UK matched-betting platform today.
18+ · Data product for licensed operators. Please gamble responsibly.
bet365 odds data
bet365 has no public API, so there are two honest routes to its odds: own the collection, or license a feed that already includes bet365 matched against exchange lay prices. Here's how to choose.
· 5 min read
bet365 odds data
bet365 is the book everyone wants and the hardest to cover well. This is the complete picture: what bet365 odds data is, what good coverage looks like, and how to put it to work without owning the collection problem.
· 5 min read
Buying vs building
Collecting your own odds works until a book changes. Then it's a treadmill of breakage, stale prices and on-call, for no product differentiation. Here's when teams stop and buy a feed instead.
· 5 min read