SportAPI
Betting platforms

Turnkey Sportsbook vs Building on APIs: Time, Cost and Control, and Which to Choose

Three ways to launch a sportsbook: a turnkey platform, your own build on odds and bet APIs, or an embedded widget. What each costs, how long it takes, who keeps control, and how to switch later.

Scales with a question mark between a ready-made platform with dashboards and a platform being assembled from code blocks; a clock, coins and sliders below

There are three ways to launch a sportsbook, and the right one depends on two facts about you: whether you have a developer, and whether you already have a site with users. With a developer and a clear idea of the product, build on APIs: the odds feed from $30 a month, bet placement and settlement from $300 a month, and about seven working days to a working betting cycle. With an existing site and no appetite for front-end work, embed the sportsbook widget and keep your accounts. Without an in-house team and with a product of your own in mind, order a turnkey sportsbook platform built around your project, with the player interface, back office and integrations delivered as one product.

The three routes don’t exclude each other. All of them run on the same SportAPI services underneath: Sport Line API for events and odds, the Coupon API for placing and settling bets. A project that starts on the widget can move to its own interface later without changing a single match or coupon identifier. Below is what each route includes, what it costs, how long it takes, and a checklist for choosing.

What “turnkey sportsbook” means, and what it never includes

A turnkey sportsbook platform is a product built around your project rather than a template you log in to. On the SportAPI side it includes:

  • a responsive player-facing website with events, markets, odds, a bet slip and personal sections;
  • a back office for users, roles, coupons and settlement statuses, project settings, integrations, an operations log and reports;
  • the sports line and bet processing, connected through the same APIs a developer would use;
  • account workflows, languages for the markets you enter, payment integrations for your country;
  • deployment, configuration and support of the technical launch.

What it never includes, from any vendor, is the part that makes you an operator. A licence in your jurisdiction, contracts with payment providers, player money and the rules of your market stay with you. At SportAPI, player balances, deposits, withdrawals and payouts remain inside your system by design: the platform receives bet and settlement statuses and your side moves the money. Betting products are for licensed operators and adult players, and advertising follows the rules of the audience’s country.

The three routes side by side

Build on APIsEmbedded widgetTurnkey platform
Time to a working product~20 minutes to the first screen with real events; ~7 working days for odds, bets and settlement with one developerThe time to add a container and the loader to a page, plus the events your site handlesAgreed after requirements and architecture; six stages from reference to deployment
Upfront costYour developer’s timeYour developer’s hours for the embed and session eventsA project estimate after a short discussion of scope
Monthly costOdds feed from $30 per sport; Coupon API from $300Agreed with the manager for the projectThe SportAPI services the platform uses, plus hosting and support in the agreed format
Who writes the codeYouAlmost nobody: embed.js and a few event handlersSportAPI’s project team
Interface controlFull: your design, your flowsThe widget’s interface in your languages, inside your pageYour design or a reference sportsbook adapted to your brand
Back officeYours to build or buyYour existing adminIncluded: users, roles, coupons, settings, integrations, reports
Player accounts and balancesYoursYours: the widget asks your site for login, session and balanceYours: the platform handles bets, your system holds the money
Best forA team that wants control and a product of its ownA site or app that already has users and needs a betting sectionA new operator without a development team who needs a complete product

Two things are the same in every column. The data and the bets come from one source, so odds, markets and settlement behave identically whichever route you take. And the money never passes through SportAPI: you own the balances in all three cases.

Route 1: build on APIs with your own team

This is the route with the most control and the most predictable price. Your backend talks to two APIs: the odds feed for the menu, events, markets and live updates, and the Coupon API for placing coupons and receiving settlement by a signed callback. The interface, the accounts and the payments are yours.

The numbers are public. The odds feed starts at $30 a month for one sport, prematch and live included, with a free two-day test key on all sports. Bet placement and settlement start at $300 a month. With the ready examples, the first screen with real events takes about 20 minutes; the full cycle takes one developer about seven working days, and a team that knows betting systems does it in about five. The day-by-day plan, with the code for each step, is in our article on integrating a sportsbook API in 7 days.

Choose this route when you have at least one backend developer, you want your own product, and you’d rather pay monthly for data than pay once for a platform. It’s the wrong route when nobody on the team can own a server: the API key, the partner credentials and the callback handler have to live on a backend you control.

Route 2: embed the sportsbook widget

The sportsbook widget is a complete betting interface, upcoming and live events, markets, odds and a bet slip, that loads inside your existing page through a JavaScript loader. You add a container and embed.js, pass the project identifier, language, sportsbook mode and a customer token when a session is required, and handle a few events: login requests, bet slip changes, balance updates, expired sessions. Your platform keeps the accounts, sessions and business logic; the widget renders the sportsbook.

It fits an online casino adding sports, a sports portal turning odds pages into an interactive section, a prediction site that wants a bet slip next to its tips, or a new project that wants to test demand before investing in a custom platform. There’s a live demo of the widget you can open before talking to anyone.

The trade-off is the interface. It’s the widget’s interface, responsive and localized, inside your page, not a design of your own. If a custom look and custom flows are the product, this route is a first step, not the destination. Pricing for the widget is agreed per project with the manager, which is also where you ask for the approved domain and the project identifier.

Route 3: a turnkey platform built around your project

The turnkey route is for a team that has a market, a business model and often a reference sportsbook it likes, but no developers to build it. The platform is assembled around your requirements: proven components are reused where it makes sense, while the interface, modules, integrations and operating scenarios are configured for your business. You can show any sportsbook as a visual reference; its layout, navigation and user journeys are reproduced and then adapted to your brand, colours and rules.

The work goes in six stages: the reference interface, requirements and architecture, prototype and design, development, testing, deployment. The timeline comes after the requirements and architecture are agreed, and the estimate after a short discussion of scope. What drives the price is the number of player pages and custom design, the back-office modules your team needs, the external integrations (payments, authentication, analytics) and the infrastructure and support format. Payment integrations are planned per country and estimated separately.

Choose this route when you need your own complete product and don’t want to hire a team to build and maintain it. Don’t choose it to save time on a first experiment: the widget does that faster, and the platform makes sense once the business case is proven.

Hidden costs in each route

Comparisons usually stop at the sticker price. These are the costs that appear in month two:

  • A settlement engine, if you build it yourself. Asian handicaps, voids, resettlement and player props are weeks of work. On the API route the Coupon API settles every market; building your own is the most expensive line nobody budgets for.
  • Live data handling. One poller for all players, caching, request limits and the prematch-to-live transition are a few days on the API route and a frequent source of outages when skipped.
  • Payments and verification. Not in any route’s base price. Providers, fees and KYC depend on the country and are contracted by you.
  • Back-office tools. On the API route you build them or adapt your admin; on the widget route you use what you have; the turnkey route includes them.
  • Operations. Odds monitoring, support, limits, bonus abuse: a person, not a feature, in every route.
  • Hosting and maintenance. The API route puts it on your server; the turnkey route agrees the infrastructure and support format up front.

A checklist for choosing

Answer these eight questions and the route usually picks itself:

  1. Is there a backend developer on the team? No → widget or turnkey.
  2. Is there already a site or app with registered users? Yes → widget first.
  3. Is the interface the product? Your own design and flows → API build or turnkey.
  4. How is the budget shaped? Monthly spend → API build; a project budget → turnkey.
  5. When do you need the first bets? This week → widget; this month → API build; a planned launch → turnkey.
  6. Who runs operations after launch? Your team with its own admin → API build; a team that needs a ready back office → turnkey.
  7. How many markets and languages at launch? Few and growing → start on APIs or the widget; many from day one → turnkey.
  8. Is this an experiment or a committed product? Experiment → widget or APIs; committed → whichever gives you the interface you want.

Most projects land on a sequence rather than a single answer: the widget to validate demand, the API build when the product needs its own interface, or the turnkey platform when the business is proven and the team wants to stay small.

Switching routes without losing anything

Because all three routes run on the same services, switching is a front-end decision, not a data migration. Sports, tournaments, matches, markets and selections carry the same identifiers in the widget, in your own interface and in the turnkey platform, and settlement statuses mean the same thing everywhere. Store coupon codes and results on your side from the first bet, and the history stays with you whatever interface places the next one; a team that built on APIs can hand the interface and back office to the turnkey route later without re-mapping sports or markets.

The one thing to plan from day one, in every route, is where the money lives. Keep balances, deposits and payouts in your system from the first bet, and any later change of interface leaves the financial side untouched.

How SportAPI fits each route

RouteSportAPI servicesFirst step
Build on APIsOdds feed + Coupon API, documentation with examples in four languages, a version for AI coding agentsA test key and the quick integration guide for the Coupon API
Embedded widgetSportsbook widget on the same feed and Coupon APIOpen the live demo, then get the project identifier from the manager
Turnkey platformThe turnkey sportsbook platform with the feed, Coupon API, widget, results, tracker and video connected as neededDescribe the market, the modules and a reference interface to the project team

Whatever the route, the sports line and the settlement are the same product. That’s what makes the choice reversible: you’re choosing who builds the interface, not who supplies the sportsbook.

FAQ

Is a turnkey sportsbook a template?

No. The platform is assembled around your requirements. Proven technical components are reused where practical, and the interface, modules, integrations and operating scenarios are configured for your project. You can also give an existing sportsbook as a reference for layout and user journeys.

How long does a turnkey platform take?

The schedule depends on the interface scope, the back-office modules and the number of integrations. A realistic timeline is given after requirements, architecture and delivery stages are agreed. For a fixed answer on timing, the API route is the one with public numbers: about seven working days for one developer.

Does SportAPI hold player balances in any of the routes?

No. In all three routes balances, deposits, withdrawals and payouts stay inside your system. SportAPI supplies the sports data, accepts and settles bets, and returns statuses; your side moves the money.

Can I start on APIs or the widget and order the platform later?

Yes. Sports, matches, markets and selections keep the same identifiers across the routes, so nothing is re-mapped. Keep coupon codes and results in your own system and the history stays with you; only the interface and the back office change.

What if I have no developers at all?

Take the widget if you already have a site with users, or the turnkey platform if you need a product of your own. Both need almost no code from your side; the widget needs a few event handlers on the page.

What does the API route cost in the first month?

A free two-day test key, then from $30 a month for the odds feed for one sport and from $300 a month for bet placement and settlement. Plans are listed on the product pages; the manager confirms them before you switch to a production key.

Decide this week

Write down the answers to the eight questions, and the route is usually obvious. If it’s the API build, get a test key and run day one of the integration plan today. If it’s the widget, open the demo and send the manager your domain. If it’s the platform, describe the market, the modules and the reference interface to the SportAPI project team on Telegram: the scope and the next steps come back from that conversation.

← All articles