OddsJam API: Pricing, Coverage & a Free Alternative

Q: How many sportsbooks does OddsJam cover?

OddsJam's API product page claims over 100 sportsbooks. OddsPapi returns 361 bookmakers from its /v4/bookmakers endpoint as of April 2026, including Asian sharps like Singbet and SBOBet and Brazilian regulated books that US-focused APIs typically skip.

Q: Does OddsJam's API include historical odds?

Yes. OddsJam markets a Full Historical Odds Database with opening, closing, and live line-movement data as part of the API product. It is included in the API tier, but that tier is quote-only. OddsPapi includes historical odds on its free tier.

How To Guides April 20, 2026

OddsJam API Pricing: What’s Actually Disclosed

OddsJam is one of the best-known names in US-facing sports betting. Most developers first meet it as a consumer product — the +EV scanner, the arbitrage finder, the line-shopping tables. What’s less obvious is that OddsJam also sells a Sports Betting API aimed at traders, syndicates, and operators.

The catch: OddsJam does not publish API pricing on its website. Their API product page lists features — over 100 sportsbooks, streaming feeds, historical database, auto-grading — and then pipes you into a “Contact us for pricing” form. You cannot get a number without a sales conversation.

That’s frustrating if you’re a developer trying to scope a project. You’re comparing APIs on price, rate limits, and coverage — not on how quickly a BDR returns your email.

This post breaks down what OddsJam’s API offering actually covers based on public sources, and shows how to build the same core workflows — line shopping, +EV detection, arb scanning — against OddsPapi’s free tier, which publishes everything upfront and includes 350+ bookmakers with historical data.

OddsJam Consumer Pricing (For Context)

OddsJam’s consumer subscription tiers are published, so you can at least price those. These are the tools bettors use directly — they are not the API product, but they’re the best public signal for how OddsJam thinks about pricing.

Tier	Monthly Price	Positioning
Gold	~$199/mo	EV+ scanner, arb finder, line shopping
Platinum	~$999/mo	Adds Circa Vegas, global books, live scanning
Industry / API	Quote only	Developer access, streaming feeds, historical database

Consumer pricing sourced from third-party reviews of oddsjam.com/subscribe; API pricing is not publicly disclosed. Verify at oddsjam.com/subscribe before committing.

For a solo developer or a small team bootstrapping a betting tool, even the Gold tier is a real commitment before you know if your strategy works. The API tier is an unknown.

OddsJam API vs OddsPapi: Head-to-Head

Here’s the side-by-side based on publicly-disclosed features:

Feature	OddsJam API	OddsPapi
Public pricing	❌ Contact sales	✅ Published tiers + free tier
Bookmaker count	“100+ sportsbooks”	361 bookmakers (verified Apr 2026)
Sharp books (Pinnacle, Singbet, SBOBet)	Pinnacle claimed; Singbet/SBOBet not disclosed	✅ All three
Historical odds database	✅ (API tier — quote only)	✅ Free tier included
Streaming / push feeds	✅ SSE (tier-gated)	✅ WebSocket on standard plans
Free tier	❌ (7-day trial on consumer product)	✅ 250 requests/month, no card
Target audience	Professional traders, syndicates, operators	Individual developers, quants, small teams
Documentation access	Gated behind contact form	Public at docs.oddspapi.io

Let’s dig into the gaps that matter most if you’re trying to build something.

Pricing Transparency: The Real Developer Blocker

Opaque pricing is a problem for a reason most enterprise sales teams underestimate: developers scope projects in public.

When you’re evaluating an API at the side-project stage, you’re not going to book a call. You’re going to open the pricing page, read the tiers, and make a decision in under five minutes. If the only option is a contact form, you close the tab and move on.

That’s the core dev-ergonomics wedge:

OddsPapi publishes everything — tier breakdowns, request limits, bookmaker count, WebSocket access, historical retention. You can build a cost model before you ever log in.
OddsJam’s API is quote-only. You have to talk to sales to find out if it fits your budget. For a team of one, that friction is the end of the evaluation.

This isn’t a criticism of OddsJam’s go-to-market — quote-only pricing makes sense if your buyers are operators and syndicates with procurement teams. It’s just a bad fit for the way individual developers work.

Bookmaker Coverage — 100+ vs 361

OddsJam’s API page claims “over 100 sportsbooks.” That’s respectable and concentrates on US-regulated books plus the major internationals. For an operator pricing player props on DraftKings and FanDuel, 100+ is plenty.

For an arbitrage or value-betting workflow, more books means more price divergence — which means more edge. OddsPapi returns 361 bookmakers live from /v4/bookmakers as of April 2026, spanning categories that are typically missing or under-represented in US-centric APIs:

Category	OddsPapi slugs (examples)
Sharp (global)	`pinnacle`, `singbet`, `sbobet`
Soft (US)	`draftkings`, `fanduel`, `betmgm`, `caesars`, `betrivers`
Soft (EU/UK)	`bet365`, `williamhill`, `ladbrokes`, `unibet`
Exchanges	`betfair-ex`, `matchbook`, `smarkets`, `polymarket`
Crypto / offshore	`1xbet`, `stake`, `bc.game`, `cloudbet`
Brazil (regulated)	`estrelabet`, `betano`, `stake.bet.br`, `pixbet`, `kto`

The Asian sharp books (singbet, sbobet) are the ones that matter most for sharpening a model. Pinnacle alone gives you one sharp signal. Cross-referencing Pinnacle, Singbet and SBOBet lets you triangulate true probability on soccer and basketball markets far more reliably.

Historical Data: The Free-Tier Wedge

OddsJam’s API product page markets a “Full Historical Odds Database” with closing lines, opening odds, and live line changes. That’s a strong feature — it’s critical for backtesting and ML training. But it’s on the API tier, which is quote-only.

OddsPapi includes historical odds on the free tier. That’s a hard differentiator for any developer who needs to validate a strategy before committing to a paid plan. A live pull against /v4/historical-odds returned 132 price snapshots for a single Pinnacle FTR outcome on a random EPL-adjacent fixture — full tick-level price history from the time the market opened.

If you’re building a betting model and you can’t backtest it, you don’t have a model — you have a hypothesis. Free historicals collapse the evaluation loop from “negotiate a contract, then backtest” to “backtest tonight.”

What OddsJam Does Well

Credit where it’s due — OddsJam has real strengths, especially on the consumer side:

+EV scanner UX: Their consumer EV scanner and arb finder are polished, purpose-built tools. If you’re a bettor who wants a GUI and alerts, OddsJam is legitimately one of the best options.
US market depth: Strong coverage of US-regulated books and player props for NFL, NBA, MLB, NHL.
Auto-grading and deep links: The API advertises bet auto-grading, deep links to sportsbooks, and real-time line movement — all valuable for operator-grade products.
Enterprise positioning: If you’re an operator with procurement, a budget, and a need for SLAs, OddsJam’s quote-only approach is probably a feature, not a bug.

None of that changes the fact that a solo developer prototyping a value-betting model or an arb bot is going to have an easier time on OddsPapi’s free tier.

Building OddsJam’s Core Workflows on OddsPapi

OddsJam’s headline features are line shopping, +EV detection, and arb scanning. All three reduce to the same primitive: pull the same market from multiple books and compare prices. Here’s how to do that against OddsPapi’s free tier in about thirty lines of Python.

1. Authenticate

import requests
from datetime import datetime, timedelta, timezone

API_KEY = "YOUR_API_KEY"  # grab a free key at oddspapi.io
BASE_URL = "https://api.oddspapi.io/v4"

# Auth is a query parameter, not a header
sports = requests.get(
    f"{BASE_URL}/sports",
    params={"apiKey": API_KEY},
).json()

print(f"{len(sports)} sports available")

2. Pull Upcoming Soccer Fixtures

# sportId 10 = Soccer (see /sports for the full catalog)
today = datetime.now(timezone.utc).date()
fixtures = requests.get(
    f"{BASE_URL}/fixtures",
    params={
        "apiKey": API_KEY,
        "sportId": 10,
        "from": today.isoformat(),
        "to": (today + timedelta(days=5)).isoformat(),
    },
).json()

# Keep upcoming fixtures that actually have odds priced
upcoming = [
    f for f in fixtures
    if f.get("hasOdds") and f["startTime"] > datetime.now(timezone.utc).isoformat()
]
print(f"{len(upcoming)} upcoming fixtures with odds")

3. Fetch Odds from Three Sharp Books

fixture = upcoming[0]
fixture_id = fixture["fixtureId"]

odds = requests.get(
    f"{BASE_URL}/odds",
    params={
        "apiKey": API_KEY,
        "fixtureId": fixture_id,
        "bookmakers": "pinnacle,singbet,bet365",
    },
).json()

# The live odds endpoint nests under bookmakerOdds
books = odds.get("bookmakerOdds", {})
print(f"Books returned: {list(books.keys())}")
# Books returned: ['bet365', 'singbet', 'pinnacle']

4. Line Shop the Full Time Result (Market 101)

# Market 101 = Full Time Result (1X2)
# Outcome IDs: 101=Home, 102=Draw, 103=Away
print(f"{fixture['participant1Name']} vs {fixture['participant2Name']}")
print(f"{'Book':<10} {'Home':>7} {'Draw':>7} {'Away':>7}")

best = {"home": (0, None), "draw": (0, None), "away": (0, None)}

for slug, book in books.items():
    try:
        outcomes = book["markets"]["101"]["outcomes"]
        h = outcomes["101"]["players"]["0"]["price"]
        d = outcomes["102"]["players"]["0"]["price"]
        a = outcomes["103"]["players"]["0"]["price"]
    except (KeyError, TypeError):
        continue
    print(f"{slug:<10} {h:>7.2f} {d:>7.2f} {a:>7.2f}")
    if h > best["home"][0]: best["home"] = (h, slug)
    if d > best["draw"][0]: best["draw"] = (d, slug)
    if a > best["away"][0]: best["away"] = (a, slug)

print(f"\nBest prices: {best}")

Real output from a live call against Liverpool vs Paris Saint-Germain (UCL, April 2026):

Liverpool FC vs Paris Saint-Germain
Book         Home    Draw    Away
bet365       2.35    4.33    2.45
singbet      2.42    4.15    2.50
pinnacle     2.40    4.44    2.45

Best prices: {'home': (2.42, 'singbet'), 'draw': (4.44, 'pinnacle'), 'away': (2.50, 'singbet')}

5. Detect an Arbitrage

# 2-way or 3-way arb check: if sum(1/best_price) < 1, you have an arb
inv_sum = 1/best["home"][0] + 1/best["draw"][0] + 1/best["away"][0]
margin_pct = (1 - inv_sum) * 100

if inv_sum < 1:
    print(f"ARB: {margin_pct:.2f}% guaranteed return")
else:
    print(f"No arb. Overround {-margin_pct:.2f}%")

That’s a full line-shopper, best-price finder, and arb detector in under 40 lines of code — built on an API that doesn’t require a sales conversation to get started.

Pull Historical Odds for Backtesting

# Historical odds for the same fixture, tick-level
# Max 3 bookmakers per call on /historical-odds
history = requests.get(
    f"{BASE_URL}/historical-odds",
    params={
        "apiKey": API_KEY,
        "fixtureId": fixture_id,
        "bookmakers": "pinnacle",
    },
).json()

# Note: top-level key is 'bookmakers' (not 'bookmakerOdds')
# and players["0"] is a LIST of snapshots (not a single dict)
snapshots = (
    history["bookmakers"]["pinnacle"]
    ["markets"]["101"]
    ["outcomes"]["101"]
    ["players"]["0"]
)
print(f"{len(snapshots)} Pinnacle FTR home price snapshots")
print(f"Opening: {snapshots[-1]['price']} @ {snapshots[-1]['createdAt']}")
print(f"Current: {snapshots[0]['price']} @ {snapshots[0]['createdAt']}")

That historical endpoint is the one that most competing APIs either charge extra for or gate behind an enterprise tier. On OddsPapi it’s on the free plan.

FAQ

Is there a free OddsJam API?

No. OddsJam’s consumer product offers a 7-day trial on subscription tiers, but the API product is quote-only and not publicly priced. If you need a genuinely free tier to prototype against, OddsPapi offers 250 requests/month with no credit card.

How much does the OddsJam API cost?

OddsJam does not publish API pricing. Access is gated behind a contact-sales form on oddsjam.com/odds-api. Consumer subscription tiers (Gold ~$199/mo, Platinum ~$999/mo) are publicly listed but cover the scanner product, not developer API access.

How many sportsbooks does OddsJam cover?

OddsJam’s API product page claims “over 100 sportsbooks” covering major US and international books. OddsPapi returns 361 bookmakers from /v4/bookmakers as of April 2026, including sharp Asian books like Singbet and SBOBet and Brazilian regulated books that US-focused APIs typically skip.

Does OddsJam’s API include historical odds?

Yes — OddsJam markets a “Full Historical Odds Database” with opening, closing, and live line-movement data as part of the API product. It’s included in the API tier but that tier is quote-only. OddsPapi includes historical odds on the free tier.

Is OddsPapi a good alternative to OddsJam for building an EV or arb bot?

Yes, for most solo developers and small teams. OddsPapi publishes all pricing, includes Pinnacle/Singbet/SBOBet as sharp reference books, ships historical data on the free tier, and documents its REST API publicly. OddsJam’s scanner UX is strong if you want a GUI tool, but if you’re building something yourself, OddsPapi removes the sales-call friction.

Ready to Start Building?

If OddsJam’s quote-only pricing is what’s stalling your project, you don’t have to wait for a sales call.

OddsPapi gives you:

361 bookmakers live right now — Pinnacle, Singbet, SBOBet, Betfair Exchange, Polymarket, Brazilian books, crypto books, the full stack
Real-time WebSocket feeds on standard plans
Free historical odds with tick-level price history for backtesting
Published pricing and a working free tier — 250 requests/month, no credit card
Public REST docs at docs.oddspapi.io

Get your free OddsPapi API key and start building tonight.

New to OddsPapi? Read What is OddsPapi? for a full breakdown of features, pricing, and coverage.