Cards Odds API | Booking Points and Card Markets

What you actually need cards odds for

Anyone searching for a cards odds API is usually trying to solve one of a few problems: comparing total booking points across bookmakers, tracking how a match's card line moves before kick off, or feeding a tipster board that covers disciplinary markets alongside goals and corners. Cards odds change often, vary a lot between bookmakers, and are easy to get wrong if you're pulling numbers by hand or scraping pages that change layout without warning. A proper feed means your comparison table, alert system or research tool is working from numbers that are actually current, not from a screenshot someone took an hour ago.

Total cards and booking points

Over/under lines on match cards and total booking points are the backbone of most cards betting content. You need these refreshed regularly enough that a comparison page or alert tool isn't showing stale numbers by kick off.

Player booking and sending off markets

Player to be booked, first card, and sending off markets add detail that pure totals miss. These are useful for tipster tools and match previews that go deeper than a single team line.

Bookmaker comparison, not a single source

Cards lines can differ noticeably between bookmakers, especially for niche player props. A feed covering multiple UK bookmakers lets you build genuine best-odds comparisons instead of quoting a single price as if it's the market.

What breaks when you scrape it yourself

Bookmaker sites change their markup, throttle requests, or hide card markets behind extra clicks, which quietly breaks scrapers. A dedicated cards odds API keeps returning structured data in the same shape, so your product doesn't fail silently on a Saturday afternoon.

Endpoints for cards odds

Discover card markets, then fetch with package=full.

GET /v1/football/events?schedule_date=YYYY-MM-DD&has_odds=true&per_page=10 GET /v1/football/events/EVENT_ID/odds?package=full&odds_format=decimal GET /v1/football/events/EVENT_ID/markets?group=cards

Replace EVENT_ID with an event_id from the events endpoint.

Example cards market shape

Decimal odds and normalised selections.

{ "event_id": "evt_123", "odds_format": "decimal", "markets": [ { "key": "total_cards", "name": "Total Cards", "outcomes": [ { "name": "Over 3.5", "odds": 1.85, "bookmaker_code": "UO004" }, { "name": "Under 3.5", "odds": 2.00, "bookmaker_code": "UO022" } ] } ] }

What you can build with cards odds

Cards data works well as one layer in a wider product rather than a standalone feature. Teams use it to build cards-specific comparison tables that sit next to goals and corners, price alert tools that flag when a booking line moves past a threshold, and tipster dashboards that track disciplinary trends across a season. It also suits research tools that back-test how referees or fixtures tend to run card-heavy, giving content and betting tools something more useful to say than a single tip.

Backtest a cards model against real bookmaker history

Historical odds are available on the Pro plan, so you can pull past cards totals and bookings lines for completed fixtures and check how your model would have performed before you stake anything on it.