Solution
A feed built for live arbitrage.
Arbitrage is a latency game: the wider and more current your market picture, the more discrepancies you can act on before they close. OddsRelay delivers a broad, normalised, timestamped board with exchange context, on a tight refresh cycle and with cache-friendly delivery, so your detection runs on the freshest data we can stand behind.
The problem
Live arbitrage needs two things that pull against each other: breadth (many books, in one shape) and freshness (current enough to act on). Build it yourself and you are integrating and maintaining dozens of independent sources, normalising every book, and fighting your own polling costs — all before you have written a line of detection logic. And the moment your data lags, the opportunity is gone.
The approach
OddsRelay hands you the market picture, not the pipeline. A broad UK board, every book normalised to one event and selection model, exchange back/lay prices alongside, refreshed on a tight cycle with a timestamp on every payload. Delivery is built to keep frequent polling cheap — ETag/304 and gzip — so you stay current without drowning in egress. You write detection; we keep the board wide and fresh.
What is included
Breadth in one shape
Many UK books normalised to a single event and selection model — the wide surface arbitrage detection needs.
Exchange context
Exchange back/lay prices alongside bookmaker odds, the reference back/lay arbitrage calculations require.
Timestamped freshness
A tight refresh cycle with a processed-at time on every payload, so you always know how current a price is.
Cache-friendly delivery
ETag/304 and gzip keep frequent polling efficient instead of ruinously expensive.
Integration
- Authenticate with a scoped or_live_* key (Bearer token).
- Pull the normalised board for a market and region in one GET, exchange context included.
- Run your cross-book and back/lay detection directly — one schema, no reconciliation.
- Poll on the matcher cycle with If-None-Match to stay current and cheap.
The full envelope, every field, scopes and rate limits live in the API docs.
Proof
Powers a leading UK matched-betting platform.
This is a production-grade feed on a proven delivery contract — a real, live board, not a benchmark.
Live coverage, freshness and status are published on the coverage dashboard.
Questions
How current is 'live' here?
The feed refreshes on a tight cycle and timestamps every payload. We describe freshness by what we can stand behind and publish it live on the coverage dashboard, rather than claiming an unverifiable 'real-time'.
Why does delivery efficiency matter for arbitrage?
Arbitrage means polling often. Without ETag/304 and gzip you re-download an unchanged board every poll, which gets expensive fast. With them, you poll frequently and only pay for what changed.
Do I get exchange prices?
Yes — exchange back/lay prices are available alongside bookmaker odds, which back/lay arbitrage calculations depend on.
Will an opportunity still be live when I act?
That depends on the market, not the feed — prices move. OddsRelay's job is to give your detection the widest, freshest, timestamped picture possible; acting in time is your tool's.
Keep reading
Near-real-time vs delayed
What odds freshness actually means, how to measure it, and how much you really need.
Coverage, freshness & reliability
How to verify the three claims every odds feed makes — and the proof to demand for each.
Arbitrage & trading tools
Cross-book and back/lay data current enough to act on — one feed, bet365 and exchange context included.
Developers
A predictable REST feed you integrate in an afternoon — no SDK, no collection to run, no matching engine.
For live arbitrage
When latency is everything: what a live-arb feed needs, and where OddsRelay honestly fits.
For arbitrage
What an arbitrage feed needs — breadth, freshness, exchange context — and where OddsRelay fits.
Use cases
Detect on the freshest board we can give you.
Start a free trial of the full UK feed, bet365 and exchange context included, and run your detection live.