Odds API · 6 October 2026 · updated 13 October 2026

How to Remove the Bookmaker Margin: Devig Methods Compared

To remove the bookmaker margin, convert every outcome's decimal odds to an implied probability (1 divided by the odds), add them up to get the book, then scale those probabilities back so they sum to exactly 100%. The fair odds are 1 divided by each rescaled probability. That rescaling step is where methods differ: the multiplicative method shrinks every outcome by the same proportion, while the additive, power and Shin methods take more of the margin off longshots. On a close two-way market the choice barely matters. On a six-runner market it can move a longshot's fair price from 42 to 89.

This guide works through the maths in decimal odds, shows where each method breaks, and maps it onto the fields an odds API returns.

Step 1: measure the book

A bookmaker's prices for every outcome of a market, turned into probabilities, add up to more than 100%. The amount above 100% is the overround, also called the vig or juice (Wikipedia: Mathematics of bookmaking).

Take an illustrative AFL head-to-head market priced at 1.40 for the home side and 3.00 for the away side:

OutcomeDecimal oddsImplied probability (1 ÷ odds)
Home1.4071.43%
Away3.0033.33%
Book104.76%

Two numbers come out of that total, and they are often confused:

  • Overround is the book minus 100%: here 4.76%.
  • Margin is the share of all stakes the bookmaker keeps if money comes in exactly in proportion to the prices: 1 minus (1 ÷ 1.0476), which is 4.55%.

Report one and label it. A dashboard that mixes the two will disagree with itself by a few tenths of a percent on every market.

Margins compound in multis

Each leg of a multi carries its own book, and the books multiply. Wikipedia's worked example takes two tennis matches, each priced at a 109.09% book, and shows the double carrying an overround of about 19.01% (Wikipedia: Mathematics of bookmaking). If you build a multi or same game multi pricer, devig each leg first, then combine the fair probabilities. Taking the margin off the combined price instead gives a different and less defensible number.

Step 2: pick a devig method

Every method takes the implied probabilities and returns a set that sums to exactly 1. They differ in who pays for the margin. The R package implied documents eight of them with formulas (CRAN: implied). These four cover most production use.

Multiplicative (also called basic, proportional or normalisation)

Divide each implied probability by the book. Every outcome is shrunk by the same proportion, so a favourite gives up more percentage points than a longshot.

  • Pros: one line of arithmetic, always stays between 0 and 1, easy to explain.
  • Cons: ignores the favourite-longshot bias, the long-observed pattern where longshots are overbet and favourites underbet (Wikipedia: Favourite-longshot bias). The implied documentation describes the basic method as the most common and generally the least accurate (CRAN: implied).

Additive

Subtract the same amount, (book minus 1) divided by the number of outcomes, from every implied probability.

  • Pros: takes proportionally more off longshots, which leans toward the favourite-longshot bias.
  • Cons: can produce negative probabilities when a market has many outcomes and the longshots are priced long (CRAN: implied).

Power

Raise every implied probability to the same power k, and search for the k that makes them sum to 1. Because k is above 1 whenever the book is over 100%, small probabilities shrink faster than large ones.

  • Pros: always stays between 0 and 1, handles any number of outcomes, solved with a simple numeric search.
  • Cons: can overcorrect longshots while moving mid-priced outcomes less than Shin does.

Shin

Shin's model assumes a share of the money comes from bettors with inside information and that the bookmaker prices defensively against them. You solve iteratively for that share, called z, and the fair probabilities fall out. On a market with only two outcomes it gives the same answer as the additive method (CRAN: implied).

  • Pros: the strongest published evidence. Štrumbelj found probabilities from Shin's model were more accurate forecasts than basic normalisation or regression models, across several team sports (International Journal of Forecasting, 2014).
  • Cons: needs an iterative solve, and z is a model parameter, not something the bookmaker publishes.

Worked example: a two-way market

Same illustrative prices, 1.40 and 3.00, run through all four methods:

MethodHome fair probabilityHome fair oddsAway fair probabilityAway fair odds
Multiplicative68.18%1.4731.82%3.14
Additive69.05%1.4530.95%3.23
Power (k = 1.081)69.51%1.4430.49%3.28
Shin (z = 0.048)69.05%1.4530.95%3.23

The spread on the outsider runs from 3.14 to 3.28. That is enough to change whether a bookmaker's 3.20 looks above or below fair. If your tool flags prices against a fair line, the method is part of the result and belongs in your output next to it.

Worked example: a six-runner market

Multi-runner markets show the real differences. Here is an illustrative six-runner market with a 123.12% book, chosen to make the gaps visible:

Decimal oddsImpliedMultiplicativeAdditivePower (k = 1.164)Shin (z = 0.052)
2.2045.45%2.712.402.502.54
3.0033.33%3.693.393.593.54
4.5022.22%5.545.445.765.55
8.0012.50%9.8511.5611.2410.92
15.006.67%18.4735.5423.3624.88
34.002.94%41.86negative60.5588.77

Three things to take from it:

  1. Multiplicative is kindest to longshots. It leaves the 34.00 runner at a fair 41.86, because it takes the same proportion off everyone.
  2. Additive breaks. The equal share it subtracts (3.85 percentage points) is bigger than the longshot's whole 2.94%, so the probability goes to minus 0.91%. Any code using it on wide markets needs a guard.
  3. Shin and power disagree most at the tail. Both move the favourite in, but Shin pushes the 34.00 runner out to almost 89.

None of these is the "true" price. They are different assumptions about where the bookmaker loaded its margin. Test them against outcomes before trusting one, which is what historical odds data is for.

Doing it against the SockOdds API

Devigging needs every outcome of the market at the same moment. Three practical rules:

  • Fetch the whole market at once. GET /v1/events/{id}/odds returns each market once, with every outcome and every bookmaker's price on it, and the time each price was seen.
  • Prices are already decimal. Sum 1 ÷ decimal_odds across one bookmaker's prices on the market. Each price also carries its implied_probability.
  • Devig one bookmaker at a time. Each outcome lists its prices best first, so the first price on each outcome can come from a different book. Mixing those best prices into one market can push the book below 100%, and then no method gives a sensible answer. Group the prices by bookmaker first.

SockOdds returns each bookmaker's own prices with their margin in them. It does not return a margin-free price, so you choose the method. This program measures each bookmaker's book on the winner market of a Rugby League World Cup game and applies the multiplicative method:

const response = await fetch("https://api.sockodds.com/v1/events/ev_000ckk0sxm2x/odds?markets=winner", {
  headers: { Authorization: `Bearer ${process.env.SOCKODDS_API_KEY}` },
});
const { data } = await response.json();

// Regroup the market's prices by bookmaker: each bookmaker's own price on every outcome.
const books = new Map();
for (const outcome of data.markets[0].outcomes) {
  for (const price of outcome.prices) {
    if (!price.available) continue;
    if (!books.has(price.bookmaker)) books.set(price.bookmaker, []);
    books.get(price.bookmaker).push({ name: outcome.name, decimal_odds: price.decimal_odds });
  }
}

for (const [bookmaker, outcomes] of books) {
  const book = outcomes.reduce((sum, o) => sum + 1 / o.decimal_odds, 0);
  const fair = outcomes.map((o) => `${o.name} ${(o.decimal_odds * book).toFixed(2)}`);
  console.log(`${bookmaker}: book ${(book * 100).toFixed(2)}%, fair ${fair.join(", ")}`);
}
import json, os, urllib.request

request = urllib.request.Request(
    "https://api.sockodds.com/v1/events/ev_000ckk0sxm2x/odds?markets=winner",
    headers={"Authorization": "Bearer " + os.environ["SOCKODDS_API_KEY"]},
)
with urllib.request.urlopen(request) as response:
    data = json.load(response)["data"]

# Regroup the market's prices by bookmaker: each bookmaker's own price on every outcome.
books = {}
for outcome in data["markets"][0]["outcomes"]:
    for price in outcome["prices"]:
        if price["available"]:
            books.setdefault(price["bookmaker"], []).append({"name": outcome["name"], "decimal_odds": price["decimal_odds"]})

for bookmaker, outcomes in books.items():
    book = sum(1 / o["decimal_odds"] for o in outcomes)
    fair = ", ".join(f"{o['name']} {o['decimal_odds'] * book:.2f}" for o in outcomes)
    print(f"{bookmaker}: book {book * 100:.2f}%, fair {fair}")

Example output · sample prices, not real odds

playup: book 100.09%, fair Australia 1.81, New Zealand 2.23
tab: book 102.37%, fair Australia 1.81, New Zealand 2.23
sportsbet: book 105.31%, fair Australia 1.81, New Zealand 2.23
neds: book 107.25%, fair Australia 1.81, New Zealand 2.23

The multiplicative fair price is the bookmaker's price times its book. Swap in the power or Shin step from above when the market has a clear favourite or a long tail.

Which method to use

SituationReasonable defaultWhy
Two-way, prices near evenMultiplicativeMethods barely differ, simplest wins
Two-way with a clear favouriteShin (equals additive here)Accounts for the favourite-longshot bias
Three-way marketsShin or powerStay inside 0 to 1, adjust the draw and outsider
Many runners, long tailPower or Shin, never additiveAdditive can go negative
Benchmark you must explain to usersMultiplicativeTransparent and easy to reproduce

Whichever you pick, store the method and its parameter (k or z) alongside the fair price. A fair probability without its method cannot be reproduced or audited later.

Try it on live markets

Get a free Developer key, run the program above against a game you follow, and compare the methods on its markets. Reading prices explains every field, and the positive EV use case shows where fair prices fit. Plans with more bookmakers and recorded history are on the pricing page.

Fair odds are estimates of probability, not predictions of profit. 18+ only. Please gamble responsibly.

Questions people ask

How do I calculate a bookmaker's margin from decimal odds?

Take 1 divided by the decimal odds for every outcome in the market and add them up. That total is the book. Anything over 100% is the overround: a two-way market at 1.40 and 3.00 sums to 104.76%, an overround of 4.76%.

What is the difference between overround and margin?

Overround is how far the book sits above 100%. Margin is the share of total stakes the bookmaker keeps on a balanced book, which is 1 minus 1 divided by the book. A 104.76% book is a 4.76% overround and a 4.55% margin.

Which devig method is the most accurate?

No single method wins everywhere. Published research found Shin's method gave more accurate probabilities than basic normalisation across several team sports, but the multiplicative method remains the most common baseline because it is simple and always stays between 0 and 1.

Why does the additive method give negative probabilities?

It subtracts the same amount from every outcome. In a market with many runners and a big overround, a longshot's implied probability can be smaller than that equal share, so it goes below zero.

Do the devig methods give different answers on a two-way market?

Only slightly when prices are close to even, and more as the favourite shortens. On a two-outcome market the additive and Shin methods give the same result.

Sources

On our guide site

Fast Odds API is our guide site, with lists, tutorials and tools. On this subject it has fair odds explained, with a calculator.

Search across the SockOdds documentation and catalogue.