Spreadex API
Pull Spreadex pre-match football odds as clean, structured data, on their own or lined up against other UK bookmakers in one schema. Built for teams who need odds they can query, not a page they have to read.
bookmaker_codes=UO024 Bookmaker code UO024. Filter any odds endpoint to Spreadex alone or blend it with other UK bookmakers.
Why Spreadex odds as data
Spreadex does not publish a public odds API, so anyone building a comparison table, alert system or tipster tool has had no clean way to pull their football odds automatically. Developers end up copying numbers by hand or building fragile scripts that break the moment the site changes. Structured Spreadex odds data matters because it lets you treat their odds the same way you treat any other bookmaker, something you can query, filter and refresh on a schedule. That is the gap UK Odds API fills.
Show Spreadex odds next to other UK bookmakers on match winner, BTTS and totals markets so users can spot the best odds at a glance. One schema means you do not need separate logic for each bookmaker.
Trigger notifications when Spreadex odds move on a fixture or market you are tracking. Structured data means you can poll on a schedule instead of refreshing a page manually.
Feed Spreadex odds into staking models or value bet calculators alongside other UK bookmakers. Consistent fields across bookmakers make the maths straightforward.
Track how Spreadex odds move for a fixture over time relative to the rest of the market, useful for building historical datasets or spotting pricing patterns. No manual note-taking required.
The DIY trap
Scraping Spreadex odds means fighting layout changes, session and login requirements built for account holders, and rate limits that were never designed with automated access in mind. A script that works today can silently return stale or empty data tomorrow, and you often will not notice until a user complains. Exchange platforms in particular are built for people placing bets, not for machines extracting structured data at scale. That is a maintenance burden most product teams do not want to own.
Layouts and XHR payloads change without notice. Proxies, CAPTCHAs, and rate limits add cost and downtime.
Automated extraction is typically prohibited. For a commercial product, a managed feed is the cleaner path. See legal risks of scraping.
The simple path
UK Odds API turns Spreadex into bookmaker code UO024, one entry in a wider UK football odds feed alongside other UK bookmakers. Filter to Spreadex on its own, or pull it side by side with the rest of the market in one consistent schema, so you are not writing custom parsing logic for an exchange that was never built to be scraped. Pre-match odds across major markets update on a schedule you can rely on.
Some products only need Spreadex on its own, for example a widget showing their exchange odds on a specific fixture. Others need Spreadex sitting alongside every other UK bookmaker so users can compare the whole market in one table. Both are the same underlying feed, you just choose whether to filter down to Spreadex or leave it in the mix with everyone else.
Most customers run on Pro (£149/mo, 7-day trial): 34 UK bookmakers, advanced markets including player props, historical odds. Start with a trial, then call the endpoints below.
How to integrate
Once you have an API key, the flow is the same for every UK bookmaker: list fixtures, request odds, optionally filter to Spreadex.
List events for a date and select an event_id.
Fetch odds and filter to Spreadex via bookmaker_codes=UO024.
Copy-paste these requests.
GET /v1/football/events?schedule_date=YYYY-MM-DD&has_odds=true&upcoming=true&per_page=10
GET /v1/football/events/EVENT_ID/odds/best?odds_format=decimal&bookmaker_codes=UO024Replace EVENT_ID with an event_id returned by the events endpoint.
A compact example response (shape is normalised across bookmakers).
{
"event_id": "evt_123",
"odds_format": "decimal",
"bookmakers": [
{ "code": "UO024", "name": "Spreadex" }
],
"markets": [
{
"key": "1x2",
"outcomes": [
{ "name": "Home", "odds": 2.05, "bookmaker_code": "UO024" },
{ "name": "Draw", "odds": 3.40, "bookmaker_code": "UO024" },
{ "name": "Away", "odds": 3.75, "bookmaker_code": "UO024" }
]
}
]
}Realtime data
Get pre-match football odds from Spreadex and other UK bookmakers as structured data, ready for your product.
Bookmakers covered
Spreadex odds data, alongside every major UK football bookmaker, in one API.
Pricing
Pick a plan based on how much odds data your product needs. Every plan includes Spreadex alongside the rest of our UK football bookmaker coverage.
£79/month
Billed today · no trial
For prototypes and early builds
£149/month
7 days free · £0 due today
For production apps and dashboards
£359/month
Billed today · no trial
For arbitrage tools and revenue-generating systems
FAQ
Spreadex does not publish a public developer API for pulling pre-match football odds into your own product. Teams usually either scrape the website (fragile and against typical Terms of Service) or use a bookmaker odds API such as UK Odds API.
You can try, but scrapers break when the site changes, hit anti-bot controls, and usually violate Terms of Service. For production apps, a managed odds API is simpler and lower risk than maintaining a Spreadex HTML parser.
Call fixtures with /v1/football/events, then odds with bookmaker_codes=UO024. Remove the filter to compare Spreadex against the wider UK market.
UK Odds API is a UK-first REST API for pre-match football odds across major UK bookmakers and exchanges - one OpenAPI contract, stable UO### codes, best-odds helpers, and advanced markets (including player props) on Pro.
Most production apps use Pro (£149/month, 7-day Pro trial): 34 UK bookmakers, core + advanced markets, historical odds. Arbitrage endpoints are on Business.
Yes. Start a 7-day Pro trial at ukoddsapi.com/sign-up, then try endpoints in the OpenAPI playground at api.ukoddsapi.com/docs.