SportAPI
Betting platforms

Sportsbook Back Office: What a Bookmaker Management System Must Include

Eight modules of a sportsbook back office: users and roles, the line, coupons and settlement, finance, limits, integrations, an operations log and reports. What the API supplies and what stays with you.

A monitor with a sportsbook back-office dashboard: a turnover chart, live matches with odds, a user list and module tiles

A sportsbook management system, the back office, is the operator’s workplace, not the players’ storefront. It has eight modules: users and roles, the line, coupons and settlement statuses, finance, limits and risk, integrations, an operations log and reports. Leave one out and the operator starts doing it by hand: in spreadsheets, in support chats, in direct edits to the database. That’s what breaks first on a busy evening.

Half of the data these modules need isn’t produced by the back office, it’s received. The line, the markets, bet statuses, settlement reasons and coupon history come from the API; what stays on your side is people, money and rules. Below is what each module must contain, where its data comes from, and which design mistakes cost the most. In the SportAPI turnkey sportsbook platform these modules are built together with the player interface; if you’re building a platform on the APIs yourself, the list below is your specification.

Why you need a back office when the API settles the bets

Automated settlement answers one question: did the bet win. It doesn’t answer the rest. Who is allowed to bet and how much. Which sports to show in this country. What to do when a player disputes a result. Which employee may change a balance, and whether that’s visible afterwards. What the day looked like in numbers.

All of those decisions live in the back office. It doesn’t repeat the API’s work, it wraps it in the operator’s rules: the API says “coupon 000000000272 won 18.50”, the back office knows who the player is, whether they’re over a limit, whether this coupon was already paid and who reviewed the dispute. That’s why in a ready-made platform the management system is designed together with the player interface instead of being bolted on after launch.

Eight modules and where their data comes from

ModuleWhat it doesData source
Users and rolesPlayer accounts, staff, access rightsYour system
The lineWhich sports, tournaments and languages to show; featured matchesSport Line API
Coupons and settlementThe list of bets, their statuses, settlement reasons, resettlementsCoupon API
FinancePlayer balances, deposits, payouts, the partner balanceYour system + Coupon API
Limits and riskMaximum stake and payout, odds-change policyYour system + Coupon API settings
IntegrationsKeys, callback, payment services, connection healthYour system + the account method
Operations logWho changed what and whenYour system
ReportsTurnover, payouts, margin, rejections, settlement speedYour system on API data

Module by module, here’s what each one can’t work without.

Users and roles

Two lists of people that must never be mixed: players and staff.

For players the back office keeps the profile, verification status, bet and payment history, restrictions (self-exclusion, limits requested by the player) and risk flags. For staff it keeps roles with different rights: support sees coupons and history but doesn’t edit balances; finance confirms payouts; the risk manager changes limits; the administrator manages integrations and keys. Every staff action goes to the log.

The minimum to build in from day one: separated roles, two-factor login for staff, and no balance edits from the same screen where balances are viewed. Betting is for adults, and verification rules come from the regulator of the country the operator works in, so the profile fields are designed for a specific jurisdiction.

The line: what players see

Operators don’t edit odds and markets; they come from the feed, and a coupon is accepted at the odds the player saw. The control here is different: what to show and where.

  • Sports and tournaments. The feed returns only what’s in the subscription and on the schedule right now: the menu method gives the current sport → country → tournament hierarchy. The back office stores the exceptions: tournaments hidden for this market, tournaments promoted to the home page.
  • Featured matches. The topmatches and topchampionships methods return curated lists of top matches and popular championships for prematch and live; the operator decides whether and where to show them.
  • Languages. Team, tournament and market names come in the language of the request; the project’s language list is a setting, not a manual translation.
  • Blocked selections. The oc_block field closes a selection in the feed automatically; the back office only needs to make sure the interface shows no button.

There’s no operator margin in this model: the margin is already inside the feed’s odds, and a coupon is always accepted at the feed’s odds; a value altered on the operator’s side is either rejected or replaced with the current one. It’s a limitation, and it’s also what removes an entire trading desk from the operator’s payroll.

Coupons and settlement statuses

The busiest screen in the back office. Support opens it dozens of times a day, so it must show everything that comes with a coupon: code, player, time, stake, type (single or accumulator), legs with odds, coupon status and the status of each bet, settlement reason, settlement date, payout.

Coupon statuses in the Coupon API:

CodeMeaningFinal
0Active or partially settledNo
2WonYes
4LostYes
8Fully refundedYes
15Returned for recalculation, a new result is comingNo

Each bet inside the coupon has its own status: win, loss, return, half win, half loss, awaiting recalculation. Next to the status sits settlement_reason_code, a stable reason code: match postponed, match cancelled, refund by market rules. That’s what support shows the player instead of “the system decided”.

Two rules that belong in the screen itself. The payout comes from real_win only, never from potential_win. And status 15 means an already paid coupon is about to be resettled: the back office shows it as a separate state, debits the stake again and waits for the new result. How settlement works inside and which markets it covers is in our article on automated bet settlement.

For history and reconciliation the API returns a coupon by code, the list of active coupons, coupons settled in the last minutes, and a selection by codes (up to 100 per request) or by creation period (up to 24 hours). That’s enough for the coupons screen not to depend on whether a callback arrived.

Finance: the money is always in your system

Player balances, deposits, withdrawals and payouts don’t pass through SportAPI in any scenario. The Coupon API accepts the bet and returns a status; your system moves the money. The finance module follows from that:

  • a player’s balance changes only through your system’s transactions: a reserve at placement, a debit at acceptance, a payout from real_win, a refund on cancellation;
  • every transaction references the coupon_code and, at settlement, the batchId of the callback batch, so a redelivered batch never creates a second payout;
  • separately from player balances, the back office shows the partner balance in the Coupon API (GET /api/partner/balance): when it runs out, new coupons get error 507, and that should be visible before players start complaining;
  • amounts are stored as decimals and coupon codes as strings, because a 12-digit code can start with zeros.

Payment providers, fees and verification are connected per country and estimated separately even in a turnkey platform; that’s the part the operator chooses.

Limits and risk

Some limits are set by the API, the rest by you. An accumulator holds at most 15 legs and can’t contain two bets on the same match, including its halves and corners; such a coupon gets 506. The odds-change policy is a coupon setting too: reject refuses the bet when the odds move and shows the new price, accept with a mode_type takes increases only, decreases only, or any change.

Everything else is the operator’s rules in the back office: maximum stake and maximum payout per coupon, limits per player and per market, separate limits for live, a stop list of events. A useful screen is “rejections today” by error code 501–507: it shows where players hit moving odds and where they hit your limits.

Integrations

This module is for the administrator, not for support. It holds the feed key, the Coupon API partner credentials, the callback URL and secret, payment service settings and the health of every connection. Secrets stay on the server and are never shown in full in the interface.

The feed’s state is checked with the account method: it returns the key’s terms, the sports and languages in the subscription, IP and site restrictions, the address the requests come from, and the request counts for the last 7 days. When the integrations screen shows the key’s expiry date and the request counter, half of the “the line disappeared” incidents are solved before anyone calls support.

The callback needs two indicators: when the last batch arrived and how many batches were redelivered. Redeliveries are normal, the API resends on timeouts and server errors, but each one must be processed once, by batchId.

Operations log

The log answers “who did this”. It records balance, limit, role and settings changes, manual corrections, payouts and cancellations, staff logins and integration changes. Every entry has an author, a time, an object, the old value and the new value.

The log isn’t only for disputes with players. It’s the basis for any external audit and the only way to reconstruct what happened after an incident where a callback arrived twice and an employee “fixed the balance by hand”.

Reports

The minimum set without which the operator guesses instead of managing:

ReportWhat it showsBuilt on
Turnover and payoutsStakes and payouts by dayYour transactions + real_win
MarginStakes minus payouts by sport, tournament, marketCoupon statuses and events_data
RejectionsShare of refused coupons by code 501–507Responses of coupons/place
Settlement speedTime between the end of the event and calculate_dateCoupon data
ResettlementsCoupons with status 15 and their outcomeCoupon statuses
CallbackDelivered, redelivered and lost batchesbatchId and your log
PlayersActive, new, limited, self-excludedYour system

Reports are built on data already present in the coupons: sport, tournament, market, odds, the score at placement and at settlement. Nothing extra has to be requested; store the whole coupon at acceptance and at settlement.

What the API supplies and what stays with the operator

Comes from SportAPIStays with the operator
The line: sports, tournaments, matches, markets, odds, blocksWhat to show in each country
Bet acceptance with an odds checkLimits per player, market and coupon
Coupon and bet statuses, settlement reasons, real_winThe payout and the player’s balance transactions
Resettlement and a signed callbackIdempotent processing by batchId
The partner balancePlayer balances, deposits, withdrawals
Key terms, restrictions, request counterStaff, roles, the log, reports

The same boundary holds in the turnkey platform: SportAPI supplies data and statuses, the operator manages people and money.

Back-office design mistakes

  1. The site first, the back office “later”. Later is the first disputed bet with nobody able to look into it. The coupons screen and the log are needed by the first real player.
  2. Paying from potential_win. Before settlement the field shows a possible win; payouts come from real_win only.
  3. One balance for everything. The partner balance in the Coupon API and player balances are different entities with different owners.
  4. Manual edits without a log. A balance correction without an author and a reason turns every dispute into one word against another.
  5. A second payout on a redelivered callback. A batch can arrive twice; a unique index on batchId is mandatory.
  6. One role for all staff. Support must not be able to change limits, and the risk manager must not be able to pay out.
  7. Limits the player interface doesn’t explain. If your limit rejects a bet, the player should see the reason, not “error”.

How it’s assembled in the SportAPI turnkey platform

In the turnkey sportsbook platform the management panel is designed together with the player interface and brings the operator’s daily workflows into one control centre: users and roles, coupons and settlement statuses, project configuration, connected integrations, an operations log and reporting sections. The exact set of sections is defined by the project specification: it’s one thing for an operator with one country and two languages and another for a network of several brands.

The line and bet settlement inside the platform are the same Sport Line API and Coupon API that developers use when they build a platform themselves. So the module list above fits both: for a platform customer it’s the checklist for the scoping conversation, for an in-house team it’s the specification. If you decide to build a module yourself, the statuses and payouts section of the Coupon API documentation is its foundation.

FAQ

Do I need a back office if I only take the sportsbook widget?

Your current admin is enough for the widget: it passes login, bet slip and balance events to your site, and accounts and money stay with you. A full coupons and reports module becomes necessary once you place your own bets through the Coupon API.

Can odds be changed in the back office?

No. Odds come from the feed, and a bet is accepted only at the feed’s odds: the API doesn’t take an altered value. The operator controls what to show and the limits, not the price.

How are disputed bets handled?

From the coupon data: the bet status, settlement_reason_code, the score at placement and at settlement. If a correction is still needed, it’s made as a transaction in your system with an author and a reason in the log; the settlement result in the API isn’t edited.

Which reports does a regulator require?

It depends on the jurisdiction, and that’s a question for the operator’s lawyer. Common to all of them: an operations log with authors, exports of bets and payouts for a period, and the ability to show one player’s full history. Build CSV export in from day one.

What does the management system cost?

In the turnkey platform it’s part of the project estimate, prepared after the modules and integrations are discussed. If your team builds the platform, the back office is its work, and the data behind it is already included in the Coupon API from $300 a month and the feed from $30 a month per sport.

Where to start

Take the table of eight modules and mark what you already have, what the API will supply, and what you’ll have to build or order. The gaps usually turn out to be the log, the roles and the reports: the places with no ready data but plenty of people. If you’re choosing a turnkey platform, that list is the agenda for the first conversation: tell the SportAPI manager on Telegram which modules your team needs and ask to see how they’re assembled.

← All articles