+EV Odds API Data

Value betting APIs explained: signals, devig math, and what they return

A value betting API (also called a +EV API) is an HTTP endpoint that returns pre-calculated betting opportunities where a soft bookmaker's odds exceed the true probability implied by sharp market prices. Instead of building your own devigging and edge-calculation logic from a raw odds feed, you consume the result directly: a list of events, markets, bookmakers, and edge percentages, ready to filter and act on.

The three platforms that offer this via API for independent developers are BetBurger, RebelBetting, and OddsJam. All three use Pinnacle (and in some cases Betfair or BetInAsia) as their sharp reference benchmark. The API output from each follows a similar structure: event identifiers, the target bookmaker's odds, the sharp reference odds, and the calculated edge percentage.

This is fundamentally different from a raw odds API (like The Odds API or SportsGameOdds) that returns lines without any edge calculation. A value betting API has already done the work of normalising odds, devigging the sharp line, and computing the edge — you receive a signal, not raw data.

How +EV APIs work: devig, sharp reference, edge calculation

Every value betting API follows the same three-step logic internally:

1. Establish true probability from the sharp market

Sharp books — Pinnacle, BetInAsia, BetISN — price markets with very low margins (1–2% vig) and large position limits, meaning their lines represent near-true probability. The API removes the residual vig to produce a no-vig probability for each outcome. Common devigging methods include multiplicative (the standard), additive, and Shin devigging — each produces slightly different probabilities, which is why the same "arb" can show a different edge % across providers.

2. Compare soft-book odds against true probability

The API continuously monitors soft bookmakers (Bet365, William Hill, Unibet, 1xBet, etc.) and converts their odds to implied probability. When a soft book's implied probability is lower than the devigged sharp probability for the same outcome, that book is offering odds higher than true probability — a positive expected value bet.

3. Calculate and return the edge percentage

Edge = (soft book's true-probability-implied odds / fair odds) - 1. A 3% edge on a bet means you expect to win 3% of your stake on average over a large sample, before accounting for bookmaker limiting. The API returns this edge figure directly — you filter by your minimum threshold and act.

Concept	Formula	Example
Fair odds (no-vig)	1 / devigged probability	Pinnacle -110/-110 → 2.00 fair
Soft book odds	Raw odds from target book	William Hill +120 → 2.20
Edge %	(soft odds / fair odds) - 1	(2.20 / 2.00) - 1 = 10%
Kelly stake	edge / (odds - 1)	10% / (2.20 - 1) = 8.3% of bankroll

BetBurger vs RebelBetting vs OddsJam: API comparison

Platform	API Access Model	Required Plan	Cost	Coverage Focus
BetBurger	Self-serve token (request at /profile/api)	Combined subscription required	€319.99/mo + API add-on	EU/Global, 65+ books, 30+ sports
RebelBetting	Custom Solutions (contact sales)	Custom contract	Negotiated	EU/UK, 90+ books, custom scope
OddsJam	Self-serve (account dashboard)	Gold plan	$99/month	US + Canada, 80+ US books

BetBurger API

BetBurger provides a REST API that mirrors their web scanner: the same pre-match and live value bet signals, exposed as JSON endpoints you can query programmatically. Setup requires an active Combined subscription (€319.99/month, covering both prematch and live) plus a separate API token requested from your account at /profile/api.

Response structure: Each value bet object contains the event name and ID, sport, league, market type, bookmaker slug, odds, the Pinnacle no-vig reference, calculated ROI %, and a direct link to the bookmaker's bet page. The live endpoint and prematch endpoint are separate — both must be polled independently.

Throughput: Up to 1,800 results per minute across both endpoints. At 2% minimum edge, a typical Combined subscriber receives 50–200 qualifying opportunities per day across soccer, tennis, and basketball. Results are available up to 30 per API request.

API documentation: Prematch API docs at rest-api-pr.betburger.com/doc.html; Live API docs at rest-api-lv.betburger.com/doc.html. A web sandbox is available for debugging requests and testing filters before writing code.

Who it is for: EU/UK bettors who need wide global bookmaker coverage (65+ active books, 230+ with regional clones) and want both pre-match and live +EV signals in a single provider. The API price-per-signal is the lowest of the three providers once you already have the Combined subscription.

RebelBetting API (Custom Solutions)

RebelBetting does not offer self-service API access. Their API is available through their Custom Solutions programme — a bespoke arrangement for developers and organisations who need programmatic access to their odds and signal feeds. Contact their team via the Custom Solutions page to discuss requirements and pricing.

The Custom Solutions offering includes: odds API with up to 1 million real-time odds from 90 bookmakers, custom betting services with selected bookmakers and markets, white-label options, and custom risk monitoring services. Pricing is negotiated per contract and reflects the scope of the integration.

Who it is for: Teams building commercial betting products, white-label tools, or high-volume institutional pipelines who need EU/UK bookmaker coverage and are willing to engage in a sales conversation. Individual developers who want self-service API access should start with OddsJam or BetBurger instead.

OddsJam API

OddsJam's Gold plan ($99/month) is the most accessible self-service API entry point for North American-focused value betting. The API covers 80+ US sportsbooks and includes pre-calculated +EV opportunity endpoints alongside the raw odds database.

Response structure: OddsJam's API returns both raw odds data (per-book, per-market) and pre-computed positive-EV opportunities. The +EV endpoint includes the event, market, bookmaker, current odds, the no-vig reference odds (Pinnacle where available, blended sharp consensus otherwise), and the calculated edge. Documentation is available at oddsjam.com/api upon subscription.

Coverage: Strong for NFL, NBA, MLB, NHL, NCAA football and basketball, and player prop markets at US sportsbooks (DraftKings, FanDuel, BetMGM, Caesars, ESPN BET, and 70+ more). Limited EU/international coverage compared to BetBurger.

Who it is for: US and Canadian bettors who want a clean self-service API with immediate access. The $99/month Gold plan is the lowest entry cost for a full-featured value betting API with a self-serve activation path. No sales conversation required.

Which plan unlocks API access on each platform

Platform	Minimum Plan for API	Monthly Cost	How to Activate
BetBurger	Combined (Prematch + Live)	€319.99/mo	Subscribe → request token at betburger.com/profile/api
RebelBetting	Custom Solutions (bespoke)	Negotiated	Contact sales via rebelbetting.com/custom-solutions
OddsJam	Gold plan	$99/mo	Subscribe → API key in account dashboard

Note on BetBurger: the standard Prematch-only subscription (€79.99/month) does not include live signals. For an automated pipeline that should operate throughout the day including live events, the Combined subscription is required. The API token itself does not have a separate listed price — it is part of the Combined subscription entitlement, but you must explicitly request it.

Wiring a +EV API pipeline: step-by-step

Execution venues for +EV: where to place the bets

The API gives you the signal. Where you bet determines whether that signal translates to long-term profit. There are three execution venue categories for +EV bettors:

Soft sportsbooks (manual execution)

The +EV edge you find via BetBurger, OddsJam, or RebelBetting is specifically at soft bookmakers — Bet365, William Hill, Unibet, 1xBet, and similar — whose lines lag sharp prices. These books offer the edge but impose strict Terms of Service against automated bet placement. Most +EV bettors place these bets manually using the direct link returned in the API response. Account longevity requires acting like a recreational bettor: round-number stakes, occasional parlays, varied sports.

Sharp brokers (automation-eligible)

MadMarket and SportMarket Pro are commission-based brokers on the Mollybet network. They route bets to Asian sharp markets and do not limit winning bettors. Both offer API access, making them the preferred execution venue for fully automated +EV pipelines. The tradeoff: broker pricing tracks the sharp line closely, so the edge you identify at the soft book may be narrower or absent when placed via a broker. Use brokers for risk management and scaling; use soft books for capturing the full identified edge when possible.

Agentic execution tools

For automated orchestration, OpenClaw and Claw Arbs can serve as the execution layer between your API output and your broker accounts. OpenClaw accepts a Skill File that defines how to process BetBurger or OddsJam API responses and route qualifying bets to MadMarket or SportMarket. See the agentic trading tools page for a full comparison.

Sample Python workflow: BetBurger API → Kelly stake → MadMarket

This pseudocode illustrates the core pipeline logic. Replace the placeholder values with your actual API credentials and bookmaker account details:

import os, requests, math

# ── Config ────────────────────────────────────────────────────────────────
BETBURGER_TOKEN = os.environ["BETBURGER_API_TOKEN"]
BANKROLL        = 5000          # current bankroll in EUR
MIN_EDGE        = 0.025         # 2.5% minimum edge
MAX_KELLY       = 0.04          # cap Kelly at 4% per bet
SPORTS_WHITELIST = {"soccer", "tennis", "basketball"}

# ── 1. Poll BetBurger value bets endpoint ─────────────────────────────────
def fetch_value_bets():
    url = "https://rest-api-pr.betburger.com/api/v1/valuebets/api_bots_meta"
    headers = {"Authorization": f"Bearer {BETBURGER_TOKEN}"}
    params  = {"per_page": 30, "min_roi": MIN_EDGE * 100}  # ROI in percent
    r = requests.get(url, headers=headers, params=params, timeout=10)
    r.raise_for_status()
    return r.json().get("bets", [])

# ── 2. Filter and size each opportunity ───────────────────────────────────
def process_bet(bet):
    sport = bet.get("sport_name", "").lower()
    if sport not in SPORTS_WHITELIST:
        return None
    edge  = bet["roi"] / 100          # convert % to decimal
    odds  = bet["bookmaker_odd"]      # decimal odds at target book
    kelly = edge / (odds - 1)
    stake = min(kelly * BANKROLL, MAX_KELLY * BANKROLL)
    return {
        "event":      bet["event_name"],
        "market":     bet["market"],
        "bookmaker":  bet["bookmaker_name"],
        "odds":       odds,
        "edge":       edge,
        "stake":      round(stake, 2),
        "direct_url": bet.get("direct_link"),
    }

# ── 3. Main loop ──────────────────────────────────────────────────────────
def main():
    raw_bets = fetch_value_bets()
    for raw in raw_bets:
        bet = process_bet(raw)
        if bet:
            print(f"[EV] {bet['event']} | {bet['bookmaker']} @ {bet['odds']}"
                  f" | edge {bet['edge']:.1%} | stake €{bet['stake']}")
            # → route to MadMarket API or log for manual placement

if __name__ == "__main__":
    main()

This is a starting skeleton. A production implementation adds: deduplication against already-processed bet IDs, async HTTP for concurrent endpoint polling, a database write for every processed bet (for CLV tracking), error handling and retry logic, and a notification layer (Telegram or Discord webhook) for manual-execution workflows.

+EV API Frequently asked questions