The raw odds API that carries the lay side, not just back prices

The raw feed gives you one consistent envelope across 60+ UK bookmakers: the same response shape, the same market keys, the same structure, so you integrate one schema instead of sixty. What it deliberately does not do is reconcile the same selection across books — each book's outcomes arrive as that book labels them, its own team and runner strings, because resolving one row per selection across sixty books is exactly the matching problem the matched-betting layer, arbitrage and +EV surfaces solve for you. If you want the reconciled, one-row-per-selection view, those are the endpoints; if you want clean per-book inputs to build your own logic on, this is it. The API docs show the response shape field by field.

The differentiator over a plain aggregator is the exchange side. Where an exchange exists for the market, the raw event carries the exchange lay price and the liquidity behind it alongside the bookmaker back prices — the half most raw feeds leave you to integrate separately. The exchange-lay page covers how that side is priced, and the coverage dashboard lists every book and exchange live.

Two discovery endpoints sit under the raw feed so you can see what data exists before you request it. GET /v2/sports enumerates the sports and competitions in season; GET /v2/events lists the fixtures for a sport, each with a has_coverage flag telling you which downstream surfaces — standard, arbitrage, +EV — that event supports. Together they let a build enumerate the board, then pull raw odds for exactly the fixtures it cares about, one at a time via GET /v2/odds/event/{eventId} or in bulk via GET /v2/odds/raw.

It's the shape a comparison engine, a bespoke rating model or an in-house matching pipeline wants: clean, structured inputs and full freedom over what you build from them. When you'd rather the relational work arrived done, the matched feed is the same coverage at a higher altitude.

Raw is a server-to-server surface: one HTTPS endpoint, authenticated with a Bearer token or an x-api-key header, JSON out, on a pre-match ~3s polling cycle, monitored, with published freshness. Bookmaker deep-links are off by default and enabled per key. It shares the envelope conventions of the rest of the v2 surface — a format=bare option, decimal or American odds, ISO-8601 or unix timestamps, strong ETags with 304s and gzip — so it plugs into the same client you'd write for any OddsRelay endpoint.

Raw is enablement-gated rather than a self-serve default: the raw scope is switched on for your key on request, and until it is the endpoints answer honestly — a non-raw key sees raw_not_in_scope, a key awaiting provisioning sees raw_not_enabled. bet365 is available on the raw feed as an add-on, not bundled; on the matched feed bet365 is included as standard. Raw coverage is UK today, with regions shown honestly on the regions view.