For matched-betting platforms
Odds data for matched-betting platforms.
If your product is an oddsmatcher or a matched-betting subscription, the feed is your core. OddsRelay is the matched feed itself: every row a back/exchange-lay pair, rated, with qualifying figures, across all live matcher types, bet365 included — so you ship product instead of rebuilding the matcher.
The job to be done
Run a matched-betting product on finished, reliable opportunities — without owning the collection, matching, rating and gating that produce them.
The data you need
Finished matched rows
Back/exchange-lay pairs, rated, with qualifying loss and profit — the exact shape an oddsmatcher renders.
Every matcher type
Standard, each-way, extra-place, BOG, dutching and 2Up, so your product covers every live matcher type.
bet365 included
The book your users expect in every offer list and oddsmatcher.
Actionable, gated data
Liquidity- and freshness-gated rows so users are not shown opportunities they cannot place.
How the feed fits
- The feed is the matcher: you render rows, you do not build pairing, rating or gating.
- All live matcher types come from one endpoint, selectable per request.
- Rows are gated before they reach you, so your oddsmatcher shows actionable opportunities.
- bet365 is included, and coverage is maintained as books change.
Integration shape
License the matched feed
A scoped or_live_* key for the matcher types and regions you offer.
Pull per type
GET /v1/odds/{type}?region=uk for each matcher type your product surfaces.
Render the oddsmatcher
Each row already carries a rating and qualifying figures — sort, filter and display.
Add alerts and more
Layer webhook alerts for qualifying odds on top of the same feed key.
What changes
- A complete oddsmatcher without a matching engine to maintain.
- Faster feature work, because the data layer is done.
- Coverage and freshness handled for you.
Proof
Powers a leading UK matched-betting platform.
Live coverage, freshness and status are published on the coverage dashboard.
Questions
Is this the feed, or a tool?
Both are available, but the core is the feed: the matched rows your oddsmatcher renders. Embeddable oddsmatcher and calculator widgets sit on top if you want done-for-you surfaces too.
Which matcher types can I offer?
Standard, each-way, extra-place, BOG, dutching and 2Up are live and selectable per request; price-boost is available as its volume builds.
Is bet365 included?
Yes — bet365 is included in the matched product. You license access to the data; the methods behind coverage are never part of it.
Can users be shown unplaceable opportunities?
Rows are gated on liquidity and freshness before they reach you, so what your oddsmatcher renders is actionable rather than stale or illiquid.
Keep reading
Matched-betting data
Oddsmatcher-ready rows — back/lay paired, rated, gated, bet365 included.
Done-for-you vs DIY
Skip the collection-and-matching stack, or own it — two products off the same backend.
Oddsmatcher-ready, explained
The difference between raw prices and a row you can render straight into an oddsmatcher.
Matched-betting feed checklist
A practical checklist for the feed under an oddsmatcher — matched output, bet365, gating, types and more.
Lay & exchange coverage
Why the exchange side matters as much as the bookmaker side — and what 'lay coverage' really means.
For matched betting
What separates a matched-betting feed worth building on — and where OddsRelay fits.
Use cases
Ship product, not a matcher.
Start a free trial of the matched feed, bet365 included, and render the rows your oddsmatcher needs.