Skip to content
Back office

Quickstart

Markdown

Introduction

Our NexusGGR API delivers a comprehensive and scalable gaming solution with seamless integration across a diverse portfolio of premium casino content. Operators gain instant access to 300+ Live Casino Games, 3,000+ Slot Games from 22 providers, Fish Games, 9 Spribe Mini Games, and a fully featured Sportsbook, enabling a complete entertainment ecosystem through a single integration.

Supported Providers

  • Live Casino
  • Slot Games
  • Fish Games
  • Sportsbook (FeedConstruct-style platform)
  • Mini Games

Game Library

Game List:
View Complete Game Library

Our extensive slot portfolio includes thousands of popular and high-performing titles from globally recognized providers. Players can enjoy premium graphics, innovative game mechanics, engaging bonus features, and optimized performance across desktop and mobile devices.

The live casino portfolio combines industry-leading providers to deliver a realistic casino environment with professional dealers, real-time video streaming, and interactive gameplay. From classic table games to modern game-show experiences, operators can offer a world-class live gaming experience to their players.

Key Features

Comprehensive Content Portfolio

  • 300+ Live Casino Games
  • 3,000+ Slot Games
  • 22 Providers
  • Fish Games
  • 9 Spribe Mini Games
  • Full Sportsbook Integration
  • Single API Integration

High Performance Infrastructure

  • Low-latency game delivery
  • Stable and scalable architecture
  • High availability infrastructure
  • Global accessibility
  • Real-time transaction processing

Easy Integration

  • Simple REST API implementation
  • Unified wallet support
  • Seamless user authentication
  • Fast onboarding process
  • Comprehensive developer documentation

Security & Reliability

  • Secure transaction handling
  • Reliable balance management
  • Stable gameplay experience
  • Enterprise-grade infrastructure
  • Continuous monitoring and support

Why Choose Our NexusGGR API

Our platform is designed to help operators launch and scale their gaming business efficiently. With a single integration, partners gain access to a broad range of casino products, premium game content, and a reliable backend infrastructure. Whether you are launching a new gaming platform or expanding an existing operation, our NexusGGR API provides the flexibility, stability, and content diversity required to deliver an exceptional player experience.

By combining premium live casino content, a vast slot game library, fish games, engaging mini games, and a complete sportsbook solution, our API enables operators to build a competitive and feature-rich gaming platform with minimal development effort.

Tip

Unfamiliar with the NexusGGR API? Start by understanding the GGR percentage.

Explaining GGR %

An agent (which can be an API reseller or an online casino operator) is required to purchase an API balance from us to facilitate game operations.

For example, if Agent A has a revenue share of 10%, they can purchase an API balance of $1,000 by paying only $100 in real cash. This allows Agent A to generate up to $1,000 in revenue from user gameplay using our games.

At a 10% GGR rate, if an agent deposits 100 USDT and their currency is IDR, with the USD to IDR exchange rate set at 16,000, the calculation for the API balance in IDR would be:

API Balance (IDR) = (Deposit Amount / GGR Rate) * 100 * (USD to IDR Rate)

Using the given values:

API Balance (IDR) = (100 / 10) * 100 * 16,000 = 16,000,000 IDR.

Thus, the agent would receive a balance of 16 million IDR in the API.

Agents also have the ability to create sub-agents for their clients. Sub-agents will purchase API balance directly from the agent, and their GGR (Gross Gaming Revenue) percentage will typically be higher than the agent's percentage, creating an additional profit margin.

The GGR percentage can be adjusted dynamically based on ongoing performance and business needs, allowing for flexible revenue management and strategic growth.

API Balance Calculation

As users engage with the games, the API balance will decrease based on the formula:
User Total Bet – User Total Win = Agent Win

For example:

  • If the total bet from users is 1000 BRL and the total win is 800 BRL, the API balance will be decreased by 200 BRL.
  • This means you earned 200 BRL from the users.

GGR Share

Based on the 200 BRL earned, the GGR share percentage will apply. If the share is 8%, you will pay 8% for API usage.

Agent Jackpot Mechanism

The Agent Jackpot is designed to regulate and balance the agent’s Return to Player (Agent RTP) by distributing winnings to randomly selected players. This system helps ensure that the agent's overall RTP target is maintained, even if individual player outcomes vary.

How It Works:

  1. Current RTP Logic Issue: In the standard RTP model, if all users lose consistently, the site retains the balance, and no players are able to withdraw their winnings.
  2. Agent Jackpot Adjustment: The Agent Jackpot System ensures that the agent's overall RTP (based on total user bets and total user wins) is balanced.
  3. Reward Distribution:
    • If individual user wins are too low to meet the agent’s RTP target, selected users may receive large rewards drawn from the total pool of user bets.
    • This mechanism increases the agent's RTP by ensuring that some players win substantial amounts, thereby balancing the overall payout rate.

Note

The higher the agent RTP1 relative to the user RTP1, the more frequently users will receive jackpot winnings.

Dynamic RTP Range: 1 ~ 999%

Agent-oriented RTP means that the system strictly maintains the agent RTP as a fixed benchmark. Accordingly, the total turnover generated from users is aligned with the agent RTP value. For example, if the agent RTP is set to 95% and the total user betting volume reaches 1M USD, the expected turnover would be approximately 5% (i.e., 50K USD).

After this, user RTP can be configured within a range of 1 to 999, allowing certain users to have higher RTP values, which enables them to achieve withdrawals after gameplay. However, if all user RTP values are set above 100, it will not produce the intended operational effect.

Tip

The optimal strategy is to maintain most user RTP values below the agent RTP, while selectively assigning higher RTP values (above 100) to specific users. The global user RTP setting can be managed via the top bar in the API panel.

Standard Configuration:

  • Agent RTP: 95%
  • Default RTP for All Users: Up to 90%
  • Custom RTP for Selected Users: Can be configured to exceed 100%, based on your requirements.
  1. This parameter can be adjusted directly through the top bar in the agent panel.