For developers
An odds API built for developers.
If you would rather ship features than maintain your own data pipeline, OddsRelay is the feed you integrate once and forget. One authenticated GET, predictable JSON, gzip and ETag/304 on the wire, an OpenAPI spec — no SDK to adopt and no matching engine to build.
The job to be done
Get clean, current odds into your product through a plain REST call you can read, cache and rate-limit against — without owning the collection problem.
The data you need
A predictable contract
Stable JSON, documented fields and an OpenAPI spec, so you can type your client and trust the shape across releases.
Cache-friendly responses
An ETag on every response and gzip on the wire, so If-None-Match gives you cheap 304s and your polling stays efficient.
Scoped, revocable keys
or_live_* / or_test_* keys sent as a Bearer token, scoped to the feed types and regions you use and revocable if one leaks.
A sandbox to build against
A test key and the real response envelope, so you integrate against the true shape before you commit.
How the feed fits
- One endpoint per market type, filtered by region — no per-bookmaker code paths to maintain.
- Plain REST: curl it, read it, wrap it in whatever language you already use. No SDK required.
- On the matched feed the response is already matched — each row is a back/exchange-lay pair with a rating, so there is no matching engine to write.
- Poll on the matcher cycle with If-None-Match; you are not paying to re-download an unchanged board.
Integration shape
Grab a key
Start with an or_test_* sandbox key or a trial or_live_* key, sent as Authorization: Bearer.
Call one endpoint
GET /v1/odds/{type}?region=uk — one matcher type per request, predictable JSON back.
Wire the envelope
Read opportunities[], opportunity_count and processed_at; handle ETag/304 and gzip the way you would any REST API.
Ship
Render the rows. The OpenAPI spec and API docs cover every field, scope and rate limit.
What changes
- An integration measured in hours, not sprints.
- No collection pipeline to run, no matching engine to own.
- A typed client you can trust across releases.
Proof
Powers a leading UK matched-betting platform.
Live coverage, freshness and status are published on the coverage dashboard.
Questions
Is there an SDK?
No SDK is required — it is a plain REST API. Send an authenticated GET and read JSON. If you prefer a typed client, generate one from the OpenAPI spec in whatever language you use.
How do I keep polling cheap?
Every response carries an ETag. Send If-None-Match and you get a cheap 304 until the board actually changes, and accept gzip to shrink the payload. Poll on the matcher cycle rather than per request.
What does a key look like?
Keys are or_live_* (production) or or_test_* (sandbox), sent as a Bearer token and scoped to the feed types and regions you license. Keys are sha256-stored and revocable; the raw secret is shown once at mint.
Can I try it before paying?
Yes. A sandbox key or a time-boxed trial gives you the real response envelope so you can build and verify the integration first. Start a free trial to get a key.
Keep reading
Done-for-you vs DIY
Skip the collection-and-matching stack, or own it — two products off the same backend.
Matched-betting data
Oddsmatcher-ready rows — back/lay paired, rated, gated, bet365 included.
Build vs buy
The real cost of building an odds pipeline yourself — and when buying wins.
Near-real-time vs delayed
What odds freshness actually means, how to measure it, and how much you really need.
For developers
What a developer-first odds API should give you — and how OddsRelay measures up.
API docs
The full envelope, scopes and rate limits.
Integrate in an afternoon.
Start a free trial, point curl at one endpoint, and render matched rows the same day. The API docs have every field and scope.