BTTS odds API

Both teams to score (BTTS) odds API

Both teams to score odds from UK bookmakers, structured for comparison sites, alert tools and tipster models.

Typical BTTS workflow

Find the fixture
Pull BTTS / goals markets

BTTS sits inside main match markets, so a core plan covers most of what you need. Go full if you also want BTTS combined with other lines.

Both Teams To Score Odds API

Why BTTS odds need to be structured, not scraped

Both teams to score is one of the most heavily bet markets across football leagues generally, which means the odds move often and vary a lot between bookmakers. Anyone building a comparison table, a value alert, or a tipster model needs those odds in a clean, consistent format rather than pulled by hand from bookmaker sites. Structured BTTS data lets you track how odds shift in the run up to kick off, spot where one bookmaker is out of line with the rest, and feed the numbers straight into your own scoring or staking logic. Without that structure you are left refreshing tabs and copying numbers into spreadsheets, which does not scale past a handful of matches.

Comparison tables

Show BTTS Yes and No odds side by side across UK bookmakers for every fixture in the Premier League, Championship and beyond. Users can see at a glance which bookmaker is offering the best return on a market they already understand.

Odds movement alerts

Flag when BTTS odds shorten or lengthen beyond a threshold you set, useful for spotting team news or weather affecting goal expectancy. Alerts can run continuously rather than relying on someone checking manually.

Tipster and model tools

Feed BTTS odds into a staking model or tipping service alongside your own goal expectancy figures. Consistent data across fixtures makes backtesting and live picks far easier to manage.

Research and content

Build BTTS trend pages or weekly previews that reference actual current odds rather than static text. This keeps content relevant and gives readers a reason to check back before kick off.

Where UK Odds API fits

Both teams to score odds, endpoints and sample data

Below are the concrete calls used to pull BTTS odds for UK football fixtures, including how they sit alongside other main match markets and what a typical response looks like.

Endpoints for BTTS odds

Fixtures, goals-group discovery, then odds.

GET /v1/football/events?schedule_date=YYYY-MM-DD&has_odds=true&per_page=10

GET /v1/football/events/EVENT_ID/markets?group=goals

GET /v1/football/events/EVENT_ID/odds?package=core&odds_format=decimal

GET /v1/football/events/EVENT_ID/odds/best?odds_format=decimal

Replace EVENT_ID with an event_id from the events response.

Example BTTS market shape

Yes/No selections with bookmaker codes.

{
  "event_id": "evt_123",
  "odds_format": "decimal",
  "markets": [
    {
      "key": "btts",
      "name": "Both Teams To Score",
      "outcomes": [
        { "name": "Yes", "odds": 1.80, "bookmaker_code": "UO004" },
        { "name": "No", "odds": 2.05, "bookmaker_code": "UO022" }
      ]
    }
  ]
}

What you can build

What you can build with BTTS odds

With reliable Both teams to score data behind the scenes, you can put together a comparison site that ranks bookmakers by BTTS price for every match in a round, a browser extension that flags the best current odds while someone is reading a preview, or an alert service that texts users when a fixture's BTTS odds move sharply. Tipster platforms can use the same data to check that a published tip's odds are still available before publishing, and content sites can automate BTTS statistics pages that update as odds change rather than going stale after a few hours.