The product
The odds API, already matched
Most odds APIs hand you raw prices and wish you luck with the hard part. OddsRelay delivers the finished article: every bookmaker back price already matched against a current exchange lay price, rated, with the qualifying loss computed — 60+ UK books with bet365 included as standard, across seven feed types, from one endpoint. The claim is checkable before you sign up: the coverage dashboard is live, and the docs are public.Powers a leading UK matched-betting platform.
$ curl api.oddsrelay.io/v1/odds/standard?region=uk \
-H "Authorization: Bearer or_live_••••••••••••"GET 200 · application/json
{
"event": "Arsenal v Chelsea",
"sport": "football",
"region": "uk",
"market": "match_odds",
"selection": "Arsenal",
"back": { book: "bet365", odds: 2.1 },
"lay": { exchange: "exchange", odds: 2.12 },
"rating": 98.1,
"updated_at": "2026-07-01T14:08:22Z"
}- 60+
- UK bookmakers, bet365 included as standard
- 7
- feed types from one endpoint
- 3
- exchanges on the lay side — Betfair, Smarkets, Matchbook
- ~3s
- pre-match polling cycle, monitored
The moat is the matching, not the prices
What separates a raw odds API from this one is the processing layer. Raw feeds deliver one price per book per market; anything relational — pairing a back price to the exchange lay side, computing a rating, applying liquidity gates — is left as your engineering. That layer is precisely what matched-betting platforms and arbitrage scanners spend their first year building, and what this feed ships on day one.
The lay side comes from the three liquid UK exchanges — Betfair, Smarkets and Matchbook — with liquidity attached, so a pair is real, not nominal. The exchange-lay spoke explains how that half works and why most feeds skip it.
Matched · rated
IllustrativeArsenal v Chelsea · Match Odds
Football · Arsenal
- Back · bet365
- 2.10
- Lay · Exchange
- 2.12
- Rating
- 98.1%
Paired, rated, liquidity-gated — qualifying loss and profit already computed. You render the row.
Built for a specific job? Start at your spoke
Each product page below covers one buyer's job in depth — the data it needs, what the feed delivers, and the honest caveats.
bet365 odds API
bet365 included as standard — already matched against exchange lay prices, monitored, and delivered as one clean feed.
Matched-betting odds API
Back prices already paired to exchange lay prices, with rating and qualifying loss computed — the feed an oddsmatcher renders directly.
Arbitrage betting API
Rated back-vs-lay pairs across 60+ UK books with bet365 — the data layer an arb scanner ranks, not raw prices it must first match.
Exchange lay odds API
Lay odds from Betfair, Smarkets and Matchbook — with liquidity — paired to every bookmaker back price in the feed.
UK odds API
60+ UK bookmakers with bet365 included, three exchanges for the lay side, every price already matched — the region the feed serves live today.
Deep where it counts, honest where it isn't
Coverage is deep rather than broad by design: 60+ UK bookmakers including the domestic names the big aggregators skip, normalised into one schema — the full picture lives on the UK coverage page and, live, on the dashboard. South African and Nigerian domestic books are on the roadmap, and are described as roadmap everywhere on this site — never as shipped.
If you are weighing this feed against a specific provider, the comparison hub holds honest, sourced pages — the lead one being OddsRelay vs The Odds API. Every competitor claim there is cited to the rival's own public pages and dated.
Matched, rated rows
Back price, lay price, liquidity, rating and qualifying loss in one object — the shape an oddsmatcher renders directly.
bet365 as standard
The book every UK shortlist starts with, included as standard across all seven feed types.
Proof before contact
Live coverage dashboard, public docs, self-serve trial. Everything is verifiable before you talk to anyone.
Reliability as a product
Monitored freshness, published status, defined uptime posture. The answer to the first question every B2B buyer actually has.
Integrate in an afternoon
Integration is deliberately boring: one HTTPS endpoint, per-client keys, JSON out. The docs include sample responses for all seven feed types — most teams paste them into their editor and have a first call working the same afternoon. When you outgrow the trial, the licence is scoped in a conversation, not a pricing maze; start with a free trial key or talk to us about licensing.
Questions
What makes this different from a normal odds API?
The output. Raw odds APIs deliver unpaired prices per bookmaker; OddsRelay delivers each back price already matched against a current exchange lay price with a rating and qualifying loss attached — the processed shape oddsmatchers and arb scanners consume directly, with bet365 included as standard.
Which bookmakers and exchanges are covered?
60+ UK bookmakers including bet365 as standard, matched against lay prices from Betfair, Smarkets and Matchbook. The live coverage dashboard lists every book with its current freshness — the public count lives there, not in marketing copy.
Is the feed real-time?
It is pre-match data on roughly a three-second polling cycle, monitored, with published freshness. That suits pre-match matched betting and pre-match arbitrage. We do not currently offer in-play streaming, so we do not sell it.
Which regions does the feed serve?
The United Kingdom is live today. South African and Nigerian domestic bookmakers are on the roadmap — SA first — and we deliberately describe them as roadmap rather than shipped until they are live on the dashboard.
How do I evaluate it against my current provider?
Two ways, both self-serve: the comparison hub holds sourced side-by-side pages for the main providers, and a free trial key delivers the real matched feed into your own product so you can compare rows, not marketing pages.
Test it before you commit
The dashboard shows live coverage now; a free trial key puts the matched feed in your product this week.