Fundamentals
Football odds data, explained
Football is where odds data does most of its volume. This explains the main markets, how they're structured as event, market and selections, and how matched back/lay pairs work for football.
· 5 min read
Asian handicap gives one side a goal head-start, which lets a bet half-win or half-lose. For your data that makes the line a field, not an afterthought. Here is how to model it.
Asian handicap removes the draw by giving one side a goal head-start. That head-start often comes in quarter-goal steps, such as -0.5, -0.75 or -1.0, which means a single bet can half-win or half-lose. For your data model the consequence is precise: the handicap line is part of the selection, the same match carries many lines at once, and settlement is no longer a simple win or lose. If your schema treats the line as an afterthought, Asian handicap is where it breaks.
An Asian handicap is a football market that gives one team a virtual goal advantage or deficit before kick-off, so the draw is priced out. Instead of the three-way 1X2 market (home, draw, away), you get a two-way bet: one side must overcome its handicap for your bet to win. Because there are only two outcomes to price, the odds sit close to even money, and the line does the work that the draw used to.
The line is the number attached to the team. A handicap of -1.0 on the favourite means they must win by two or more clear goals for a full win, and a win by exactly one goal returns your stake. The same match also trades at -0.5, -0.75, -1.25 and so on, each a distinct selection with its own price. The choice of line is the bet, as much as the choice of team.
Quarter lines are handicaps that end in .25 or .75, and they are the reason Asian handicap is harder to model than any three-way market. A quarter line splits your stake across the two nearest half or whole lines, so a single bet can settle as a half-win or a half-loss rather than a clean result. This is the split-stake mechanic, and your settlement logic has to represent it.
-1.0, -0.5) settle cleanly: win, lose, or, for whole lines, a stake refund on an exact-margin push.-0.75) split the stake in two: half is placed at the nearest half line, half at the nearest whole line, and the two halves can settle differently.-0.5 half wins, the -1.0 half pushes and is refunded. Net result: a half-win.The line is a first-class field on the selection. A selection is not just Arsenal: it is Arsenal at a specific handicap, at a specific price, from a specific book. The same event therefore holds many Asian handicap selections at once, one per line, and each is matched against exchange lay odds independently. Treat the line as a field and the whole market stays clean; bury it in a market name string and you lose the ability to compare lines across books.
OddsRelay delivers each Asian handicap selection with its line carried explicitly, the back price from the book, and the paired exchange lay price, so your model never has to parse a line out of free text. Here is the shape of a single -0.75 selection (illustrative, not live data):
{
"event": "Arsenal vs Chelsea",
"market": "asian_handicap",
"selection": "Arsenal",
"handicap": -0.75,
"back": { "bookmaker": "bet365", "odds": 1.95 },
"lay": { "exchange": "betfair", "odds": 1.98, "liquidity": 1420 },
"rating": 96.7,
"qualifying_loss": -0.21
// ... region, feed_type and freshness fields elided
}The handicap field is what makes the row self-describing. It says which line this price is for, so a -0.5 selection and a -0.75 selection on the same team are two distinct rows you can rate and settle separately. The back and lay pairing works exactly as it does elsewhere in the feed: bet365 covered as standard, matched against Betfair, Smarkets or Matchbook lay prices, with a rating and qualifying_loss already computed. See how the wider envelope fits together in how odds data is structured.
A 1X2 market has three fixed selections and clean win-or-lose settlement, so its data shape is simple. Asian handicap breaks both of those assumptions at once: the number of selections is open-ended, and settlement can be partial. That combination is where most home-grown schemas struggle.
| Property | 1X2 (match odds) | Asian handicap |
|---|---|---|
| Selections per event | Three, fixed | Many, one per line |
| The line | None | A first-class field on the selection |
| Settlement | Win or lose | Win, lose, push, half-win, or half-loss |
| Draw handling | Priced explicitly | Removed by the handicap |
Get the shape wrong and the failures are quiet. Two books quoting Arsenal on different lines look like the same selection until you settle them and the numbers diverge. A quarter line stored as a single win-or-lose outcome settles a half-win as a full one. These are not edge cases: they are the normal behaviour of the market, and a consistent data shape is what tames them.
That consistency is the point of a productised feed. Every Asian handicap selection arrives with the same fields in the same places: an explicit handicap, the back and lay pair, a rating and a qualifying loss. Your matcher reads one shape and renders it, instead of reconciling a different line format per book. The same discipline covers the closely related total-goals markets, which we walk through in over/under and totals data.
Asian handicap sits in the deeper football market set, alongside totals and both-teams-to-score, and it is one of the reasons matched betting and arbitrage tools reach past match odds. Because the lines are numerous and the prices sit near even money, there are more back-versus-lay pairings to scan, and more opportunities hidden across the lines. A feed that carries every line as a clean row is what makes that scannable rather than a parsing exercise. For the wider market map, see football odds data.
Coverage spans 60+ UK books with bet365 included, each Asian handicap price matched against three exchanges, with coverage built to extend into the domestic South African and Nigerian books the large aggregators tend to skip. The line is carried the same way across all of them, so adding a book never changes the shape your model reads.
Asian handicap removes the draw with a goal head-start, prices it in quarter-goal steps, and lets a bet half-win or half-lose. For your data that means the line is a field, the same match carries many lines, and settlement is partial rather than binary. OddsRelay delivers every line as a self-describing matched row, and it powers a leading UK matched-betting platform today. You can see the lines live on the coverage dashboard, or read the shape yourself with a free trial before you commit.
Written by
Founder, OddsRelay
James is the founder of OddsRelay — the odds-data feed behind matched betting, arbitrage and odds-comparison products: 60+ UK bookmakers with bet365 included, matched against exchange lay prices and delivered as one clean, documented API. He writes here about how that data layer actually behaves — coverage, matching, freshness and the trade-offs — from the side that builds and runs it. The same feed powers a leading UK matched-betting platform today.
Part of the Fundamentals cluster
What is an odds API? A 2026 guide for builders18+ · Data product for licensed operators. Please gamble responsibly.
Fundamentals
Football is where odds data does most of its volume. This explains the main markets, how they're structured as event, market and selections, and how matched back/lay pairs work for football.
· 5 min read
Fundamentals
Odds data is a four-level hierarchy: event to market to selection to price, plus bookmaker, region and freshness metadata. Once the shape clicks, integrating a feed is straightforward.
· 5 min read
Fundamentals
Over/under markets price whether goals, points or corners finish above or below a line. For data, the line is part of the selection: here is why that changes how you compare, match and arb totals across books.
· 5 min read