# Arbitrage betting vs matched betting: the data

> Arbitrage betting and matched betting read the same back and lay prices. What separates the two tools is the bookmaker offer, and the boards each one needs.

Published 21 November 2026

**Arbitrage betting vs matched betting is a difference of purpose, not of data: both back a selection at a bookmaker and cover it elsewhere, but an arbitrage tool looks for prices that disagree, while a matched betting tool looks for the closest back and lay pair to carry a bookmaker's offer.** If you build either tool, you read the same rows.

## What is the difference between arbitrage betting and matched betting?

Arbitrage betting and matched betting differ in where the gap comes from. [Arbitrage](https://oddsrelay.io/glossary/arbitrage) needs the prices themselves to disagree: a bookmaker's back price above an exchange's lay price, or back prices across bookmakers that together cover a market for less than 100% implied probability.

[Matched betting](https://oddsrelay.io/glossary/matched-betting) does not need the prices to disagree. It pairs a back bet with a lay on the same selection so that the result stops mattering, and the reason to place the pair is the bookmaker's offer attached to the back bet.

For the person building the tool, the difference sits in the filter. An arbitrage scanner keeps the few pairs whose prices cross. An oddsmatcher keeps the pairs that sit closest together and sorts them, because its user accepts a small gap on purpose to meet an offer's terms.

|  | Arbitrage tool | Matched betting tool |
| --- | --- | --- |
| Looks for | A back price above the lay, or backs that cross between bookmakers | The back and lay pair with the smallest gap |
| Depends on | Prices that disagree at the same moment | A bookmaker offer the user holds |
| Reads from the feed | `back` and `lay` on one outcome, or one back per outcome across venues | `back` and `lay` on one outcome, plus the offer boards |
| Must also check | How old each venue's prices can be, and `available` on the lay | `available` on the lay, and the offer's own terms |

What each tool looks for, depends on and reads.

## Is matched betting a form of arbitrage?

In its mechanics, yes, where the arbitrage is a back against a lay. Guides for bettors disagree about the label, and some use the two words for one thing. A builder can skip that argument, because the code settles it: one comparison, two thresholds.

On the [standard matched board](https://oddsrelay.io/products/matched-feed) in the UK & Ireland, each outcome carries bookmaker `back` offers, best price first, and `lay` offers from Betfair, Smarkets and Matchbook, lowest price first. Each lay shows `available`, the liquidity at its price. Neither tool has to match names first, because the board has already put each venue's price on the same fixture, market and selection.

GET /v2/odds/standard, one outcome · example:

```json
{
  "name": "Leeds",
  "back": [
    { "bookmaker": "coral", "price": 2.6, "link": null },
    { "bookmaker": "betfred", "price": 2.5, "link": null }
  ],
  "lay": [
    { "exchange": "matchbook", "price": 2.58, "available": 65, "link": null },
    { "exchange": "smarkets", "price": 2.62, "available": 540, "link": null }
  ]
}
```

Your code: back price B, lay price L, exchange commission c as a fraction · example:

```ts
const rating = ((B * (1 - c)) / (L - c)) * 100;

// B = 2.6, c = 0.02
// L = 2.58: rating = 99.53
// L = 2.62: rating = 98.00

const arbitrage = rating > 100;        // an arbitrage scanner keeps this pair
const closeEnough = rating >= 95;      // an oddsmatcher keeps it, at a floor its user sets
```

Here the best back, 2.6, is above the lowest lay, 2.58, yet once 2% commission comes off, your figure lands just under 100. An arbitrage scanner drops it. An oddsmatcher lists it near the top.

The feed sends the prices and computes neither figure, so the commission rate and both thresholds stay in your code, where each user's own rate lives. [Qualifying loss and ratings](https://oddsrelay.io/blog/qualifying-loss-and-ratings-explained) works the same sum through for a matched betting screen.

## Do an arbitrage tool and a matched betting tool need different odds data?

An arbitrage tool and a matched betting tool need the same prices and different extras. Both start from back and lay on one row, and both need the lay's `available` before they show a pair, because 65 at 2.58 covers a small stake and no more. [Pairing back and lay odds](https://oddsrelay.io/blog/pairing-back-and-lay-odds) picks the lay that fits a given stake.

A matched betting tool then needs the offers. Its users work through bookmaker promotions, so it reads the offer boards as well: [2Up](https://oddsrelay.io/products/2up-feed), [each-way](https://oddsrelay.io/products/each-way-feed), [extra place](https://oddsrelay.io/products/extra-place-feed) and [best odds guaranteed](https://oddsrelay.io/products/bog-feed), each a feed type of its own. 2Up and best odds guaranteed keep the standard board's fields. Each-way and extra place add the place terms and a place lay. [The guide to matched betting odds data](https://oddsrelay.io/blog/complete-guide-matched-betting-odds-data) goes through them one by one.

An arbitrage tool needs breadth and time instead. Its second check is back against back, with nothing laid. The [dutching feed](https://oddsrelay.io/products/dutching-feed) groups the prices for it: one back price per outcome, each at a different bookmaker or exchange.

A crossing pair is rare and short-lived, so the tool has to know how old each venue's prices can be before it shows one. `meta.last_seen` holds the time of each venue's last read, per sport. [What an arbitrage tool needs](https://oddsrelay.io/blog/betting-arbitrage-data) covers both checks, and [value betting vs arbitrage](https://oddsrelay.io/blog/value-betting-vs-arbitrage-data) adds the third tool that often ships beside them.

Both tools keep their core comparison in play: the standard and dutching boards take `inPlay=only` for events already under way. The offer boards stay pre-match. [Live vs pre-match odds data](https://oddsrelay.io/blog/live-vs-pre-match-odds-data) sets out what changes.

How much of this applies depends on where your users are. The matched boards and the exchange lay prices cover the UK & Ireland. In the other regions the feed serves raw bookmaker prices, so an arbitrage tool there compares bookmakers with each other, and a matched betting tool has no lay side to read.

## Build one comparison, then choose the threshold

If you are deciding which tool to build first, write the comparison once. Read one outcome from the standard board, compute the figure above at a commission rate you can change, and print every pair with its lay's `available`. Set the floor near 95 and you have the core of an oddsmatcher. Set it above 100 and you have the first check of an arbitrage scanner.

[Odds data for arbitrage and value-betting tools](https://oddsrelay.io/for/trading-tools) lists the request behind each arbitrage check, the standard board's among them. A tool other people use runs on [Enterprise](https://oddsrelay.io/enterprise), and so does one a business keeps for itself.

18+ · OddsRelay supplies odds data only and takes no bets. Please gamble responsibly.

Source: https://oddsrelay.io/blog/arbitrage-betting-vs-matched-betting
