The OddsJam API in 2026: A Complete Overview

The OddsJam API is the data layer behind one of the best known arbitrage and positive EV betting platforms in the United States. Instead of watching OddsJam's own screens and alerts, developers can license the underlying odds feeds and build their own scanners, models and tools on top of them. The setup changed meaningfully in early 2025, when the company behind OddsJam was acquired and the developer side of the business consolidated under the OpticOdds brand.

This overview explains who actually runs the API in 2026, what data it provides, how push and pull delivery differ, what people typically build with it, how access and pricing work, and where the honest limitations sit. If you want background on the consumer platform itself, start with our full OddsJam review.

OddsJam and OpticOdds: Who Runs the API in 2026

OddsJam and OpticOdds are sister brands owned by the same company, Odds Holdings. Gambling.com Group announced a definitive agreement to acquire Odds Holdings in December 2024 and completed the transaction on January 1, 2025. According to the acquirer's own announcement, the deal was worth up to 160 million dollars: 80 million paid upfront, with up to 80 million more tied to business performance through the end of 2026.

In practice, the split between the two brands works like this. OddsJam is the consumer product, selling subscriptions to bettors who want arbitrage, positive EV and promo conversion tools. OpticOdds is the developer and enterprise arm, with API documentation hosted at developer.opticodds.com and marketing aimed at sportsbooks, media companies and trading teams. OddsJam's own site still carries an odds API page describing the same family of feeds, so you will see both names attached to what is substantially one data infrastructure. OpticOdds advertises coverage of more than 200 sportsbooks on its site, while the OddsJam API page cites more than 100. Either way, the pitch is the same: breadth of bookmaker coverage that no individual could monitor manually.

What the API Actually Provides

According to the odds API page on oddsjam.com, the feed delivers real time betting odds from more than 100 sportsbooks as structured JSON or XML. The main data categories are:

• Main lines: moneylines, point spreads and totals across the major leagues, both pre-match and live.
• Player props and alternate markets: the depth that matters most for positive EV screening, since pricing errors cluster in low liquidity markets.
• Injury data: the page describes comprehensive injury reporting for the major sports leagues.
• Schedules, rosters, scores and results: the plumbing needed to map odds onto fixtures and settle bets afterwards.
• Futures: season long markets such as league winners and MVP awards.
• Historical odds: the OpticOdds developer documentation covers both real time and historical data, which is what makes backtesting possible.
• Bet grading: the same documentation lists automated settlement logic for grading bets against final results.

OddsJam also says its infrastructure processes over one million odds updates per second and markets the feed as the fastest sports betting API available. Treat statements like that as vendor marketing rather than independently verified benchmarks.

Push vs Pull: How the Data Reaches You

There are two delivery models, and the difference matters more than any other technical detail.

Pull, or REST polling, means your application requests odds from the API on a schedule you control. It is simple to build against and perfectly adequate for pre-match research, line shopping displays and model building, where being thirty seconds behind the market costs you little.

Push, or streaming, means the vendor sends changes to you as they happen. The OpticOdds documentation describes a streaming API based on server sent events, so line movements arrive without polling, plus message queue delivery through RabbitMQ for its automated trading tooling. Push is what serious arbitrage and live betting applications need: an arbitrage window can close in seconds, and a scanner that polls once a minute will mostly surface prices that no longer exist by the time you open the sportsbook.

What People Actually Build With It

• Arbitrage scanners. Compare the same market across every covered book, flag combinations where the implied probabilities sum to less than 100 percent, and calculate the stake split. This is OddsJam's own core product, rebuilt to your specification.
• Positive EV screeners. Benchmark each book's price against a sharp reference line and surface bets priced above fair value. Prop and alternate market depth is the selling point here.
• Line shopping tools. Best price displays for content sites or personal dashboards, showing where a given bet is priced most generously right now.
• Model building and backtesting. Historical odds let you test a betting model against the prices that were actually available, including closing lines, rather than guessing what you could have got.
• Grading and tracking. Results and settlement data let a bet tracker mark wagers won or lost automatically instead of relying on manual entry.

Access and Pricing

There is no self serve signup for the API. The OpticOdds getting started documentation states that a license key is issued after you fill out its contact form, and OddsJam's API page likewise routes interested developers to a contact sales flow. Neither site publishes API pricing, so the honest summary is: pricing on request, scoped to the leagues, sportsbooks, markets and delivery methods you need. Expect an enterprise style conversation rather than a checkout page.

This is separate from OddsJam's consumer subscriptions, which are a different product with plans published on oddsjam.com. If you are weighing the consumer tools rather than the raw feed, our article on whether OddsJam is worth the price covers that side.

Alternatives Worth Knowing About

If a sales gated enterprise feed is more than your project needs, the market has other layers. Betting exchanges publish their own market data streams, which reflect tradeable prices rather than collected bookmaker screens. There are also smaller independent odds API vendors selling simpler feeds with published pricing. The best known of these is The Odds API, which lists its plans openly: a free tier of 500 requests per month and paid tiers starting at 30 dollars per month, with odds from more than 40 bookmakers and historical snapshots back to 2020, according to its website. That is far narrower coverage than OddsJam advertises, but a free tier is a low risk way to prototype an idea before committing to an enterprise contract.

Limitations and Honest Caveats

A few things the marketing pages will not tell you.

• Aggregated odds lag the source. An aggregator collects prices from bookmaker sites and redistributes them, and every step adds delay. Exchange streaming feeds show prices you can actually trade at that moment; an aggregated bookmaker price may already be gone when you click through. For slow moving pre-match markets this rarely matters, but in live arbitrage it is the difference between a profit and a phantom.
• Provenance is contested. Much aggregated odds data ultimately originates from sportsbook websites that do not want to be scraped. Sportsbooks block scrapers aggressively with rate limits and bans, which is precisely why paid APIs exist: they outsource a fragile, adversarial collection problem. That tension occasionally reaches court. SBC Americas reported in January 2025 that analytics firm Swish Analytics had filed a lawsuit against OpticOdds and OddsJam alleging misappropriation of odds data. Those are allegations, not findings, but they show how contested this layer of the industry is.
• Terms of use bind you too. API licenses typically restrict redistribution, display and resale. If you plan to show licensed odds publicly on a website, confirm the license covers that before you build.
• Data does not equal profit. A faster feed does not change the underlying economics: bookmakers limit and close accounts that consistently beat their prices. The API removes the data bottleneck, not the business risk.

The Manual Counterpart: Learn the Math First

An enterprise data feed automates a calculation you should understand by hand first. The core of arbitrage is checking whether a set of odds across different bookmakers guarantees a margin, then splitting your total stake so every outcome returns the same amount. That is exactly what our free surebet calculator does. Work through a few real examples with it before thinking about APIs: once you can spot and stake an arbitrage manually, you will know precisely what a data subscription would be automating, and whether the volume you realistically bet justifies paying for it.

Responsible Gambling

Odds data, scanners and calculators reduce guesswork; they do not remove risk. Arbitrage depends on execution, account access and prices that hold long enough to bet, and none of those are guaranteed. Only stake money you can afford to lose, set deposit and time limits, and step away if betting stops feeling like a controlled, structured activity. Free confidential support is available from BeGambleAware and the National Council on Problem Gambling.