SportAPI
Sportsbook API integration

Sportsbook API integration: odds, bets and settlement

Odds feed, bet placement and bet settlement for your sportsbook: one JSON API, step-by-step documentation and API consultations from our team.

Integration guide
First event screen in ~20 min From $30/month 2 days free
Sportsbook API integration checklist with completed steps and a bet slip settled through the API
What you connect

Four parts of a sportsbook integration

Take only what your product needs: the odds feed alone, or the full cycle from odds to payout.

Odds feed

Prematch and live events, betting markets and current odds for 25+ sports and esports. From $30/month.

Sports Odds API →

Bet placement

Singles and accumulators. The API re-checks odds and outcome availability at the moment of the bet.

Coupon API →

Settlement

Coupons are settled automatically; results come by signed callback or by request. From $300/month.

Settlement docs →

Ready-made front end

No time to build the betting interface? Embed the sportsbook widget with events, odds and a bet slip.

Sportsbook widget →
What your players see

A sportsbook in your design, running on our data

Live matches with moving odds, a bet slip that checks the price before accepting the bet, and settled bets in the player's history. The design is yours; the data, odds checks and settlement come from SportAPI.

  • Live and prematch line
  • Odds move in real time
  • Odds check at placement
  • Website and mobile app
Open the live demo
Sportsbook website and mobile app with live matches, odds and a bet slip built on SportAPI data
Integration in numbers

~20min

to the first screen with real events, using our ready examples

1day

for odds, bets and settlement with an AI agent and our AI-ready docs

5–30days

for a typical in-house developer team, depending on experience

2days

of free access to all sports, prematch and live, to test the integration

How it works

From the odds on your site to the payout

Six calls cover the whole betting cycle. Your server talks to SportAPI, your players only see your interface.

  1. 01

    Sports menu

    menu returns sports, countries and tournaments for prematch or live.

    ↓
  2. 02

    Events and odds

    events and event return matches, markets and current odds.

    ↓
  3. 03

    Bet pointer

    The selected outcome is passed as a pointer with the odds the player saw.

    ↓
  4. 04

    Place the coupon

    coupons/place checks the odds and accepts a single or an accumulator.

    ↓
  5. 05

    Settlement

    After the match the coupon is settled; you get a signed callback.

    ↓
  6. 06

    Payout

    Your system credits the winnings to the player's balance.

Architecture

Players talk to you, you talk to SportAPI

Your site and app call only your backend. The backend keeps the API key, caches the line for all players, sends bets to SportAPI and receives settlement by a signed callback.

  • API key never in the browser
  • One cache for all players
  • Your balances, your rules
  • Callback signed with HMAC
Integration guide
Sportsbook API integration architecture: players, your backend, Sport Line API and Coupon API with a settlement callback
Integration plan

Six steps to launch

Steps 1–3 give you a live sports line on the site. Steps 4–6 are needed only if you accept bets through SportAPI.

1. Get a test key

Send a request in Telegram. The trial gives 2 days of access to all sports, prematch and live.

2. First request

Call menu with the key in the Package header and build the first event screen.

Open

3. Odds and live updates

Load events and odds, refresh live data at the recommended intervals, hide blocked outcomes.

Open

4. Accept bets

Get a JWT, build the bet pointer from the selected outcome and place the coupon.

Open

5. Receive settlement

Verify the HMAC signature of the callback or poll settled coupons; process each batch once.

Open

6. Go live

Choose a plan, switch to the production key and keep polling as a fallback for callbacks.

Settlement

Bets are settled without manual work

After the match every coupon gets its result automatically: win, loss, return, or half win on Asian markets. The callback brings the payout, retries never cause a double payout, and polling restores results after downtime.

  • Singles and accumulators
  • Win, loss, return, half win
  • Safe retries with batchId
  • Recovery after downtime
How settlement works
Settled coupons with win, loss, half win and return statuses and a verified settlement callback log
Code

Odds in, bet out: two requests

The odds feed uses an API key in the Package header. Bet placement uses a JWT and the pointer of the selected outcome. Full examples in cURL, Python, PHP and JavaScript are in the documentation.

cURL bash 
# 1. Live sports menu (Sport Line API)
curl 'https://YOUR_API_DOMAIN/v1/menu/live/en' \
  --header 'Package: YOUR_API_KEY'

# 2. Place a single (Coupon API)
curl -X POST "$BASE_URL/api/partner/coupons/place" \
  --header "Authorization: Bearer $CLIENT_TOKEN" \
  --header "Content-Type: application/json" \
  --data '{"list_bets": ["line#737779544#1#1#0#1.85"], "amount": 10}'
Code examples
Who does what

Your side and our side

Your side

Your server stores the API key and makes all requests. You run the player accounts and balances, the interface and the payments, and decide which sports and markets to show.

Our side

The odds feed, odds checks at placement, settlement and its delivery, documentation with examples, and API consultations. We do not write your code, but our team can build the integration for an extra fee.

Pricing

Integration costs

The odds feed is paid monthly by the number of sports. Start with a free 2-day trial on all sports. Bet placement and settlement (Coupon API): from $300/month with $20 a month for test bets. Prepay for several months and save up to 30%.

SPORT

One sport to test the integration on a real product.

$30 /month
  • Sports: 1
  • Prematch + Live
  • Languages: EN
  • Top leagues
  • Support: 8/5
★
SPORT+

Ten sports for a growing sportsbook.

$250 /month
  • Sports: 10
  • Prematch + Live
  • Languages: EN, RU
  • Top leagues
  • Support: 12/7
SPORT FULL

All sports and esports for a full sportsbook.

$600 /month
  • Sports: all
  • Prematch + Live
  • Languages: EN, RU
  • Top leagues
  • Esports included
  • Support: 24/7
FAQ

Sportsbook API integration questions

It depends on who does it. A team that knows betting systems needs about 5 days; a team new to the domain can spend a month. With an AI agent and our documentation for AI agents, we built the full cycle ourselves in one day. The first screen with real events takes about 20 minutes.
Yes. The Sports Odds API works on its own: many projects show odds and accept bets in their own system or do not accept bets at all. The Coupon API is connected separately when you need bet placement and settlement.
Yes. The API key and the client JWT must stay on your server. The browser or mobile app talks to your backend, and the backend talks to SportAPI. A front-end-only integration would expose the key.
Consultations on the API are included: we answer questions about methods, data and errors. We do not write code as part of the plan, but our team can build the integration for an extra fee — describe the project to the manager.
Run SportAPI in parallel on a trial key, map your sports and markets to ours, and switch the front end once the line matches. Bets already placed with the old provider are settled there; new coupons go through the Coupon API.
Use both. The signed callback delivers each result as soon as a bet is settled; periodic polling of recently settled coupons covers the time your endpoint was down. Process every callback batch once, because the same batch may be retried.
Any language that sends HTTPS requests and parses JSON. The documentation has ready examples in cURL, Python, PHP and JavaScript, and a Markdown version for AI coding agents.
Integration help

SportAPI team

Stuck on a method or a field?

Ask in Telegram: we explain methods, data and errors for free. If you want us to build the integration, we will estimate it separately.

Ask the team

How sportsbook API integration works

A sportsbook API integration connects your betting product to three things it cannot produce on its own: a sports line with current odds, a way to accept bets against that line, and settlement after the match. With SportAPI each part is a separate JSON API, so you can start with the odds feed and add bet placement later without rewriting the front end.

Sports betting API integration step by step

The first part is the odds feed. Your server requests the sports menu, the list of events and the full event with markets and odds, stores the identifiers and refreshes live data at the recommended intervals. Blocked outcomes must be disabled in the interface, otherwise players will try to bet on a closed price.

The second part is bet placement. When a player confirms the bet slip, your backend sends the pointer of each selected outcome together with the odds the player saw. The odds check rejects the coupon or accepts the new price according to the mode you choose, so a player never gets a bet at odds that no longer exist.

The third part is settlement. After the event the coupon is settled automatically and the result is sent to your callback with an HMAC signature. Your system credits the winnings to the player's balance and keeps polling settled coupons as a safety net.

Betting API for a sportsbook business: what to plan

Plan the server side first. The API key and the JWT never reach the browser; all requests go through your backend, which also caches the line and protects you from request limits. Decide which sports and markets you will show, how you will display odds changes, and how you will handle a coupon that was rejected.

Then plan reconciliation. A reliable integration stores every coupon code, processes each callback batch exactly once and can recover results after downtime. These three rules prevent the most expensive integration errors: double payouts and lost bets.

Integration service or in-house development

Most teams integrate on their own: the documentation covers every method with request and response examples, and there is a version written for AI coding agents. Consultations on the API are free. If you do not have developers, the SportAPI team can build the integration for an extra fee, or you can launch faster with the sportsbook widget or a turnkey sportsbook platform.

Launch checklist

Before you switch to the production key, check four things. The line on your site matches the API response for the same event, including blocked outcomes. A coupon with changed odds is rejected or accepted exactly as your chosen mode says, and the player sees why. A settled coupon credits the balance once, even if you replay the same callback. After you stop your callback endpoint for an hour, polling restores every result. If all four pass on the trial key, the integration is ready for real players.

Common integration mistakes

Calling the API from the browser and exposing the key. Refreshing live data more often than the recommended intervals and hitting limits. Treating HTTP 200 as success without checking the business code in the response. Crediting a payout twice when the same callback arrives again. Each of these is covered in the integration guide and the bet placement quick guide.