Every price on a betting app is the output of a four layer supply chain that most of the industry never sees. This is how data suppliers, trading teams, platform APIs and front ends fit together, why most operators buy rather than build, and what procurement teams test before they sign.
Key takeaways
- Four Layers: Data suppliers, trading and risk, the platform API and the operator front end each add something to a price before a customer sees it
- API Is The Product: The sportsbook API exposes catalogues, live prices, bet placement, cash out, settlement and reporting, and is the contract between vendor and operator
- Buy Not Build: Only 49 of 310 licensed operators reviewed by Gamblers Connect run a sportsbook alongside casino, and most of those licence a platform and feed
- Test Before Signature: Latency, rate limits, schema design, documentation and error handling decide roadmap speed for years, so the technical review belongs in procurement
How sportsbook odds are set: four layers between an event and a price
Anyone asking how sportsbook odds are set gets a supply chain answer rather than a maths one. A football match, a tennis set or a basketball quarter becomes a betting market through four distinct layers of supply. The first is data: a small group of specialist companies collect fixtures, statistics and live event feeds, delivered to operators as a sportsbook data feed, often under official rights deals with leagues and in some US states under mandates that require official data for in play markets. The second is trading: pricing models and human traders turn that data into odds, set margins and manage exposure. The third is the platform: a software layer that holds the markets, accepts bets, settles them and exposes everything through an API. The fourth is the front end, the web and mobile product the customer actually touches, together with the CRM, bonus and reporting systems behind it.
That odds supply chain is the same for a global brand and a regional start up. Most operators own only the fourth layer outright. Some own part of the second. Very few own the first or third, which is why the commercial structure of the sector looks the way it does.
Data suppliers and official data
Live data is the scarce input. Collection at thousands of events a day requires scouts, video rights and processing infrastructure that only a handful of suppliers maintain, and official data agreements with leagues add a licensing layer on top. In the United States, several state regulators require official league data for certain in play markets, which turns a commercial preference into a compliance requirement and gives the data layer pricing power.
Trading and risk
The sports betting trading team is the layer that converts data into prices and decides how much of each price to accept. Models produce the baseline, traders adjust for information the models miss, and risk rules set limits by market, customer and event. Operators that differentiate on price do so here, through margin and limits rather than through the raw numbers, which usually arrive from the same few suppliers.
The platform and its API
The platform is where the market lives, and the sportsbook platform API is how everything reaches it. It stores catalogues, receives prices, validates and accepts bets, settles outcomes and keeps the history. The sportsbook API is the set of endpoints through which everything else reaches it: market and selection catalogues, real time price feeds, usually streamed over WebSocket, bet placement and validation, cash out requests, settlement events, bet history and reporting extracts. Authentication typically runs on signed tokens or OAuth, with rate limits and separate credentials per environment.
The front end and everything behind it
Front end teams consume the API to render the sportsbook on web and mobile. CRM teams read betting history from it to trigger campaigns. Bonus engines check eligibility against bet records. Business intelligence teams feed warehouses and dashboards from it. Trading desk tools may use a separate internal tier with elevated permissions. Operators with custom front ends usually place a thin gateway over the vendor API to handle authentication, caching and observability.
Why most operators buy rather than build
Building a trading operation across dozens of sports and thousands of daily events is expensive and slow, so the standard model is to licence a platform and a data feed and overlay the operator’s own traders, margins and limits where it wants to differ from the market. The numbers show how rare the full stack operator is. Of 310 licensed operators reviewed by Gamblers Connect, an independent B2B iGaming media platform, as of November 2026, only 49, or 16 percent, run a sportsbook alongside their casino. Among the 22 UK Gambling Commission licensees in that directory the figure is seven; among 36 Malta Gaming Authority licensees it is eight; among 175 Curaçao licensees, 24.
A casino first operator that adds sports almost always buys it as a platform and a feed, and the API is the product it is really buying. The brand, the margin policy and the customer relationship remain the operator’s. The markets, the prices and the settlement logic arrive through endpoints.
How procurement teams evaluate an API
Most platform procurements include a technical deep dive, and the questions are consistent across operators. Schema design: are markets, selections and events modelled in a way the operator’s own systems can consume without translation? Latency: how long does a bet placement call take under peak load, and how quickly do price updates propagate? Rate limits: what happens when the front end exceeds them on a Saturday afternoon? Error handling: does a rejected bet return a reason code the front end can act on, or a generic failure? Documentation: can an engineer integrate from the docs alone?
APIs are not standardised across vendors. Each exposes a different surface, with different schemas, conventions and event models, so operators running more than one product, often for different jurisdictions, build an abstraction layer to normalise them. REST endpoints usually handle placement, catalogue retrieval and reporting, while streaming endpoints carry live prices, suspensions and settlement events. Bet acceptance latency is a closely watched metric because it is customer facing: a placement endpoint that validates against current prices, customer limits and risk rules and returns a confirmation or a reason code within tens of milliseconds is the difference between a bet taken and a customer lost.
What it means for media, affiliates and data partners
Publishers and affiliates sit on the same supply chain. Odds comparison widgets, line movement trackers and editorial tools draw on licensed feeds, and the coverage and update frequency of that licence decide how accurate the content is. A media company that understands where its odds come from, and how far behind the operator’s own feed they run, makes better decisions about what to publish and how to caveat it.
The trading desk’s view: when to override the feed
A feed gives every operator the same starting price, so the trading desk is where an operator decides what to do with it. Three decisions recur. Margin: how much to build into each market, which varies by sport, by market type and by how confident the desk is in the model. Limits: how much to accept from each customer segment on each market, which is where most of the risk management actually happens. Overrides: when to move away from the feed because the desk knows something the model does not, a late team change, a weather report, a local story that has not reached the supplier.
Latency and in play
In play markets compress all three decisions into seconds. Prices update continuously, suspensions have to fire before an event resolves, and the gap between the supplier’s feed and the operator’s displayed price is a direct exposure. Operators measure that gap and pay for lower latency, which is why the data layer and the platform layer are priced on speed as much as on coverage.
What a data licence actually covers
Data agreements vary in three dimensions a buyer should read closely. Coverage: which competitions and which markets, and whether in play is included. Rights: whether the data is official, collected under a league agreement, or unofficial, collected by scouts and video, which matters where regulators mandate official data. Latency tier: how quickly updates arrive, and whether the operator is on the same tier as its competitors. A licence that looks cheap on coverage can be expensive on latency, and the difference shows up as settlement disputes and suspended markets rather than on the invoice.
What happens next
In play betting, micro markets and same game combinations all increase the volume of prices and the speed at which they change, which pushes more weight onto the API layer. The caveat for buyers is that API quality rarely fails loudly. Shortcomings surface as roadmap friction, features that take a quarter longer than planned because an endpoint is awkward, rather than as outages. That is why the technical review belongs in procurement, not after signature, and why the platform’s API is worth more attention than its demo.
Frequently asked questions
Who sets the odds at a sportsbook?
Usually a combination of a data supplier, a pricing model and the operator’s own trading team. The supplier provides fixtures and live data, the model produces a baseline price, and traders adjust margins and limits. Few operators price every market in house; most licence a feed and a platform.
What is a sportsbook API?
The set of programmatic endpoints a sportsbook platform exposes: market catalogues, live prices, bet placement, cash out, settlement, bet history and reporting. It is the contract between the platform vendor and the operator’s front end, CRM, bonus engine and reporting systems.
How many casino operators also run a sportsbook?
Fewer than the marketing suggests. Of 310 licensed operators reviewed by Gamblers Connect as of November 2026, 49 run a sportsbook alongside their casino, including seven of 22 UK Gambling Commission licensees.
Sources
- What Is a Sportsbook API? Glossary entry covering endpoints, protocols and procurement evaluation. Gamblers Connect, June 2026. https://gamblersconnect.com/glossary/sportsbook-api/
- Online Casino Reviews by Licence, 310 operators and product coverage counts. Gamblers Connect, November 2026. https://gamblersconnect.com/casinos/
- UKGC, MGA and Curaçao licence directories, sportsbook counts by licence. Gamblers Connect, November 2026. https://gamblersconnect.com/casinos/ukgc/
Data in this article comes from the Gamblers Connect casino directory and demo catalogue as dated above and may be cited with attribution to Gamblers Connect.
