PADDY POWER ODDS DATA
Pre-match UK football odds from Paddy Power as clean, structured data, available on its own or set against other UK bookmakers in one schema.
bookmaker_codes=UO019 One bookmaker code, one consistent odds format, no scraping required.
WHY YOU NEED THIS
People search for a Paddy Power API because they want their football odds as usable data, whether that is for a comparison table, a price alert tool, a tipster site, or research on how a bookmaker prices matches. The problem is that Paddy Power does not publish a public developer API for pre-match football odds, so there is no official feed to plug into. That leaves developers checking the site by hand or attempting to scrape pages, both of which are slow and break easily. Structured Paddy Power odds data solves that gap by giving you the numbers in a consistent, machine-readable format.
Show Paddy Power alongside other UK bookmakers so users can see who is offering the best odds on a given match. This is the most common reason people look for Paddy Power odds as data.
Build alerts that notify users when Paddy Power odds move on a match or market they are tracking. Structured data makes it straightforward to compare current odds against a saved baseline.
Reference Paddy Power odds automatically in match previews, tips pages, or betting content instead of updating figures by hand. This keeps published odds accurate without daily manual edits.
Study how Paddy Power prices matches over time, or compare their odds against the wider market for research and modelling. Historical, structured data supports this far better than one-off page checks.
The DIY trap
Scraping a bookmaker site for odds looks simple until it runs in production. Paddy Power's pages are built for browsers, not data extraction, so layout changes, added scripts, or A/B tests can quietly break a scraper without any warning. Odds also move quickly around kick-off, and a scraper that only checks every few minutes will show stale numbers exactly when accuracy matters most. On top of that, you end up maintaining fragile scraping code instead of building the product your users actually want.
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 tracks Paddy Power under the bookmaker code UO019 and delivers their pre-match football odds as clean, structured JSON. You can pull Paddy Power on its own, or filter it alongside other UK bookmakers to build comparison views, all from one consistent schema. That means no page scraping, no layout monitoring, and no guessing whether a number changed.
With Paddy Power odds available as structured data, you can build a single-bookmaker product, such as a Paddy Power price tracker or alert tool, or fold their odds into a wider comparison product covering several UK bookmakers side by side. Either way, the odds arrive in the same format, so your product logic does not need to change depending on which bookmaker or how many you are showing.
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 Paddy Power.
List events for a date and select an event_id.
Fetch odds and filter to Paddy Power via bookmaker_codes=UO019.
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=UO019Replace 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": "UO019", "name": "Paddy Power" }
],
"markets": [
{
"key": "1x2",
"outcomes": [
{ "name": "Home", "odds": 2.05, "bookmaker_code": "UO019" },
{ "name": "Draw", "odds": 3.40, "bookmaker_code": "UO019" },
{ "name": "Away", "odds": 3.75, "bookmaker_code": "UO019" }
]
}
]
}Realtime data
Get pre-match UK football odds from Paddy Power and other UK bookmakers in one API, ready for comparison tools, alerts and research.
Bookmakers covered
Paddy Power odds, alongside other major UK football bookmakers, in one feed.
Pricing
Straightforward plans based on how much odds data you need, with Paddy Power included across UK football 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
Paddy Power 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 Paddy Power HTML parser.
Call fixtures with /v1/football/events, then odds with bookmaker_codes=UO019. Remove the filter to compare Paddy Power 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.