Casino Game API Cost: What Integration Actually Costs

Ask six providers what a casino API costs and you will get six answers, none of which is a number. The most common reply is a percentage. A percentage is not a price — it is a standing claim on every euro your casino earns, for as long as the contract runs.

Casino API cost is unusually hard to research because nearly everyone publishing on the subject sells revenue share. Their cost pages describe setup fees and integration timelines in detail, then handle the recurring charge in one line: "standard rev-share applies." That line is the entire cost of the deal. Everything else is rounding.

So this article does the thing those pages avoid. It puts real numbers against each pricing model, adds the engineering cost that never appears in a quote, and works the arithmetic to the point where one model overtakes the other. If you want the technical side first — wallet types, callbacks, session handling — this companion guide to how a casino game API actually works covers the mechanics. This one is about the bill.

The four ways providers price API access

Almost every offer on the market is a variation of four structures. Knowing which one you are being sold matters more than the headline figure attached to it.

Pure revenue share. You pay a percentage of gross gaming revenue, typically 8–12% direct from a studio. Setup is often free or nominal. There is no floor and no ceiling: the provider earns when you earn, and keeps earning at the same rate when you are doing ten times the volume.

Monthly minimum plus revenue share. A fixed monthly fee sits underneath the percentage. This is the most common structure for mid-sized operators. The floor typically runs €1,000–€15,000 per month depending on catalogue size and provider tier. Below a certain traffic level the floor is the whole cost, which means your effective revenue share is far higher than the number on the contract.

One-time licence per game. You pay once per title for the right to run it, usually on a single domain. No ongoing percentage. Pricing is per game and scales with production quality rather than with your success.

Outright purchase. You buy the game, host it yourself, and owe nothing further. This is the rarest structure because it requires a provider that builds its own games rather than reselling someone else's — a distributor cannot sell you what it does not own.

The first two are rentals. The last two are purchases. Almost all published comparison content covers only the first two, because the companies writing it cannot offer the other two.

The integration cost nobody puts in the quote

"Free integration" is the most expensive phrase in this industry.

It is technically accurate — the provider will not invoice you for connecting to their API. It is also beside the point, because the work sits on your side of the wall. Someone on your team has to build the wallet callback endpoints, handle session creation and expiry, reconcile bet and win transactions against your ledger nightly, run the test environment, and chase down the mismatches that show up in week three when a player disconnects mid-spin.

That is real engineering. At market rates it lands somewhere between €8,000 and €40,000 of developer time for a first integration, depending on whether your platform already speaks the pattern or you are building the wallet layer from scratch. Budget 4–8 weeks even when the documentation is good.

Here is the part most operators get backwards. They treat that integration cost as a reason to avoid direct deals and go through an aggregator instead — one connection, many studios, less work. Reasonable on the surface. But the integration is a one-time fixed cost, and the aggregator's margin is a permanent variable cost. You are trading a bill you pay once for a bill you pay every month you stay in business.

Do the integration once, properly, against a well-documented REST API, and every game you ever add afterwards is a configuration change rather than a project. The expensive part is the first one.

Aggregator or direct: the margin stacks

When you take games through an aggregator, two parties are paid out of the same revenue. The studio takes its cut of the game's GGR, and the aggregator takes a cut on top for distribution and the single point of connection.

Published aggregator terms typically run 10–20% of GGR, with 15% common. Premium studio access is frequently priced as a surcharge above that — another 2–4%, or a fixed monthly fee per studio. Then there are the line items that only appear on the invoice: per-provider activation fees, per-title certification charges when you enter a new jurisdiction, API call overages above an included tier, and separate pricing for historic data exports.

None of those are hidden exactly. They are all in the contract. They are simply not in the number you were quoted, which is why operators routinely discover that an advertised 15% behaves like 18% or more once a year of real invoices exists.

The convenience is genuine and worth paying for in some cases. Thirty studios through one connection is a real saving in engineering time. Just price it honestly: you are buying integration convenience with a percentage of revenue that never stops, and the convenience is delivered once.

The math: where buying overtakes renting

This is the calculation the rest of the market does not publish, for the obvious reason.

Take a 20-game package. Our own rental pricing is a €1,000 monthly minimum for 20 games, a €1,000 one-time setup fee, and a 4–6% share of GGR that only applies after the games have produced €100,000 in lifetime revenue. Buying the same 20 games outright at our GOLD tier is €3,000 per game — €60,000 once, then 0% forever.

Now run two operators through both models.

Operator A does €40,000 per month in GGR. Lifetime revenue passes €100,000 during month three. From there the monthly cost is the €1,000 floor plus 6% of €40,000, so €3,400. Add the setup fee and the two months before the threshold, and cumulative rental cost reaches €60,000 in month 19. After that the rental keeps charging and the purchase does not.

Operator B does €8,000 per month in GGR. The €100,000 threshold is not crossed until month 13. Before that the cost is the €1,000 floor. After it, €1,480 per month. Cumulative rental cost does not reach €60,000 until around month 44.

Monthly GGR	Rental cost, 24 months	Buy outright (20 games)	Break-even
€8,000	€30,760	€60,000	~month 44
€40,000	€77,800	€60,000	~month 19
€100,000	€163,000	€60,000	~month 10

Two operators, the same catalogue, the same contract — and the correct answer is different for each. Operator A should buy. Operator B should rent, at least until the traffic proves itself.

Run the same exercise against a standard 10% industry revenue share and the gap widens sharply. At €40,000 monthly GGR, 10% is €4,000 per month: €48,000 a year, €144,000 over three years, and it never stops. The purchase price of the same catalogue is recovered in the first fifteen months and the remaining twenty-one months are free.

Growth is what breaks the rental case. A fixed purchase price is a number that gets smaller relative to your business every month you succeed. A revenue share is a number that grows in exact proportion to your success — you are, structurally, paying a penalty for scaling.

Regulators understand this better than providers do. The Malta Gaming Authority's published fee schedule for B2C remote gaming licences charges a €5,000 application fee and a €25,000 fixed annual licence fee, then applies a compliance contribution that declines as you grow — 1.25% on the first €3 million of revenue, tapering to 0.40% at the top of the scale. The regulator takes a smaller share as you get bigger. A flat revenue share does the exact opposite.

When renting is the right call

We sell both models, and we tell operators to rent more often than the sales logic would suggest.

Rent when the traffic is unproven. If you cannot forecast next quarter's GGR within a reasonable band, a €60,000 purchase is a bet on a number you do not have. The rental floor is the cheaper way to find out whether the games convert for your audience.

Rent when you are testing a market or a vertical. Rent when your licence is provisional and might not land. Rent when cash preservation matters more than unit economics, which for a first-year operator it usually does.

Buy when the traffic is real and repeating, when you intend to run the same catalogue for more than two years, and when you want the games on infrastructure you control. The signal to watch is simple: once your monthly revenue-share payment is consistently larger than a twentieth of the purchase price, the arithmetic has already turned and you are paying for the privilege of not having decided.

In 16 years of selling casino games, the pattern we see most often is operators who rent for eighteen months longer than the numbers justify, because renting requires no decision and buying does. The gap between month 19 and month 37 on a package like the one above is roughly €61,000 of pure overpayment. Nobody sends an invoice labelled "indecision," but that is what it is.

What actually moves the price

Two operators asking for "casino API access" can receive quotes an order of magnitude apart, because the phrase covers wildly different scopes. These are the variables that do the work:

• Number of games. The single biggest driver, and the one with the steepest volume discounts. Per-game economics improve substantially between 20 and 100 titles.
• Game quality tier. Production cost varies enormously between a clean three-reel title and a flagship slot with rigged character animation and multiple bonus rounds. Our single-domain licences run €1,500 per game at the STANDARD tier up to €8,500 at DIAMOND for exactly this reason.
• Currency and market handling. Multi-currency support, crypto wallets, and dual-currency sweepstakes wiring each add configuration and testing work. Sweepstakes in particular is not a toggle — it needs separate prize pools, a frontend currency switch, and a bet/win conversion layer per mode.
• RTP configurability. Providers that ship one fixed RTP per game are cheaper than those that let you select between variants. If you operate across markets with different competitive norms, you need the range.
• Support tier. Business-hours email is included almost everywhere. Named technical contacts, guaranteed response windows, and integration engineering time are priced separately and legitimately so.
• Hosting. On a rental the provider hosts the game server and absorbs that cost inside the fee. On a purchase you host it, which means a dedicated server bill of roughly €150 per month sits on your side of the ledger. Worth including in any comparison — it is small, but it is real.

Seven questions to ask before you sign

Every one of these has cost consequences, and every one is easier to ask now than to discover later.

1. Who owns the player data? If session and wagering history sits in the provider's system rather than yours, your migration cost at exit is not zero — it may be prohibitive. That is the real lock-in, not the notice period.
2. What happens at exit? Ask specifically what you keep: game IDs, player history, configuration, the integration itself. Get the answer in writing before the answer matters.
3. Is the RNG certified, and by whom? The relevant standard for interactive gaming systems is GLI-19, published by Gaming Laboratories International. Ask which lab tested it and when. Note the precise claim you should expect: the RNG is certified, not each individual game.
4. Are PAR sheets included? The mathematical specification defining hit frequency, RTP, and volatility per title. Some providers treat these as proprietary and withhold them. You need them for regulatory filings and for understanding what you are actually running.
5. What are the rate-change terms? Can the percentage be revised mid-contract? Can studios be reclassified into a premium band that carries a surcharge? Both happen.
6. Is there a minimum monthly guarantee, and how is it calculated? A floor is a fixed cost wearing a variable cost's clothing. If you will spend most of the contract under it, price the deal at the floor, not the percentage.
7. What are the API call limits and overage rates? Per-call charges above an included tier are a standard term and a standard surprise. Multiply your projected spin volume by the overage rate before you sign, not after.

How we price it

CasinoWebScripts builds its own games — 252 active HTML5 titles across slots, table games, scratch cards, keno, and video poker, all running on a GLI-19 certified RNG. Because we own what we sell, we can offer the purchase models that distributors structurally cannot.

Rentals start at a €1,000 monthly minimum for 20 games with a €1,000 one-time setup, and the 4–6% GGR share applies only after €100,000 in lifetime revenue. Buy the games outright instead and the revenue share is 0%, permanently — the model we wrote about in detail in our piece on why operators are moving away from GGR cuts. Full source code is available for operators who want the game logic on their own infrastructure, priced per title on request.

Integration runs through a documented REST API that connects to any platform stack. Your platform does not need to be built in any particular language — the games expose endpoints, your wallet answers them. Details are on the games API integration page.

Getting to a real number

The reason casino API cost resists a single answer is that the question bundles four different commercial structures under one phrase. Resolve that first and the arithmetic becomes ordinary: what is the fixed component, what is the variable component, how long do you intend to run these games, and what does your own engineering team cost for the weeks it takes to connect them.

Work those four out and you can compare any two offers on the market in an afternoon. Skip them and you will compare percentages, which tells you almost nothing — a 6% share on a floor you never clear is more expensive than a 12% share on volume you actually do.

If you want the wider budget context, our breakdowns of total online casino startup cost and what casino software costs in 2026 cover the layers around the games, and buy versus rent works the same decision across the full platform rather than just the API. For how the games sit inside the broader stack, see our explainer on what an iGaming platform actually is.

Or skip the reading and get a priced configuration: the configuration wizard takes about two minutes and returns real numbers for your game count, market, and preferred model.

Frequently asked questions

How much does a casino API cost per month?

For a rental structure, expect a monthly minimum between €1,000 and €15,000 depending on catalogue size and provider tier, plus a revenue share on top. Our own 20-game rental starts at a €1,000 monthly minimum, with a 4–6% GGR share that applies only after €100,000 in lifetime revenue. On an outright purchase the monthly cost is your hosting bill — roughly €150 for a dedicated server — and nothing else.

Is casino API integration really free?

The provider usually does not charge for it. Your own engineering does. Building the wallet callbacks, session handling, and nightly reconciliation is typically 4–8 weeks of developer time, or €8,000–€40,000 at market rates for a first integration. When a provider advertises free integration alongside a revenue share, the integration cost is inside the percentage — you pay it monthly, forever, instead of once.

Is it cheaper to go through an aggregator or direct to the studio?

Direct is cheaper per euro of revenue; aggregators are cheaper in engineering time. An aggregator adds its distribution margin on top of the studio's cut, commonly bringing the total to 10–20% of GGR before surcharges. If you need thirty studios, the aggregator route is usually right. If you need one catalogue you will run for years, the margin stacking costs more than the integration you avoided.

At what point does buying games beat paying revenue share?

It depends entirely on your GGR, which is why no provider publishes a single figure. On a €60,000 twenty-game purchase compared against our rental model, break-even lands around month 19 at €40,000 monthly GGR, around month 10 at €100,000, and not until roughly month 44 at €8,000. The rule of thumb: when your monthly revenue-share payment exceeds about a twentieth of the purchase price, buying has already won.

What drives casino API pricing up the most?

Game count and quality tier, in that order. Beyond those, the biggest cost additions are multi-currency and sweepstakes dual-currency wiring, configurable RTP variants, per-jurisdiction game certification, and support tiers with guaranteed response times. Crypto wallet handling adds cost on top of standard fiat integration.

Do I need a gambling licence before integrating a casino API?

For real-money operations in a regulated market, yes — and the licence usually costs more than the games. Malta's B2C remote gaming licence carries a €5,000 application fee and a €25,000 fixed annual fee before compliance contributions. Sweepstakes and social casino models operate under different rules and are the common route for operators who want to launch without a gaming licence, which is why dual-currency support matters at the integration stage rather than later. Either way, budget the licence separately from your casino API cost — they are independent line items, and conflating them is how launch budgets slip.

if (basename($_SERVER['SCRIPT_FILENAME']) === basename(__FILE__)) exit;