Official website: https://aggameapi.com/
10 Years. 1 API. 1,200+ Games. More Control.
Flexible API solutions built for slot platforms worldwide.
AG has spent ten years focused on helping slot platforms integrate content, wallet workflows, and operating controls through a more efficient and flexible API solution. One API connects a catalog of 1,200+ slot games with game launch, wallet integration, records, and project-level configuration capabilities.
This repository is a public, practical guide for platform, engineering, and operations teams evaluating an integration with the AG Game Slots API. It explains the company and business scope, the main integration decisions, and the checks required before launch.
This guide complements the official API documentation with company context, solution architecture, implementation planning, and operational practices.
Public guide baseline: AG Game API V5.0.0
Last reviewed: 2026-08-16
AG builds B2B API solutions for slot platforms operating across multiple content, wallet, and regional requirements. Its work combines ten years of focused development with one integration layer intended to reduce repeated integration work and give platform teams clearer control over content scope, wallet architecture, RTP configuration, records, and rollout planning.
The current business scope includes:
- 1 API and 1,200+ slot games: organize game content through a unified integration instead of maintaining a separate technical path for every content source;
- flexible RTP configuration: manage RTP at project level across supported games and versions, aligned with the operating plan;
- two wallet models: support both single-wallet and transfer-wallet integration directions according to the platform architecture;
- 35 countries and regions: support project and integration discussions across the published global coverage list;
- global low-latency access: use a globally distributed access design to shorten regional delivery paths and support stable cross-region use;
- more operational control: connect game sessions, wallet events, transaction records, reconciliation, and project configuration in one delivery workflow.
Project onboarding aligns game availability, RTP scope, infrastructure, language, currency, and regional delivery with the selected game versions, deployment plan, and network conditions.
Read the complete AG company profile, business overview, and 35-country coverage.
| Focus | What AG provides | Platform value |
|---|---|---|
| Content aggregation | One API for a catalog of 1,200+ slot games | Reduce repeated content-integration work |
| Platform integration | Game catalog, session launch, wallet, merchant, and record workflows | Connect the core technical path through one integration model |
| Operational configuration | Flexible RTP configuration across supported games and project plans | Give platform teams more control over operating parameters |
| Wallet architecture | Single-wallet and transfer-wallet options | Fit the integration to the platform's existing balance and ledger model |
| Global delivery | Support across 35 countries and regions with global low-latency access design | Prepare multi-region rollouts with shorter access paths |
| Technical delivery | Scope review, integration preparation, testing, reconciliation, and launch support | Turn API access into an operationally testable project |
The AG Slots API portfolio brings together 11 game providers:
PGSoft · Pragmatic · Evoplay · CP Games · WG Games · JILI · TADA · JDB · FC · BG · HSD
Provider discovery, game listing, and game-session launch are organized through one integration flow. Explore the game provider directory, browse the complete 1,194-entry game catalog mapping, or use the structured game catalog JSON.
A Slots API integration connects a platform to game content and the operational flows around it. The work normally includes more than opening a game URL:
- discovering the agreed game providers, categories, and titles;
- creating a player game session and handling the return path;
- choosing and implementing a single-wallet or transfer-wallet model;
- protecting money-changing operations from duplicate processing;
- querying game and wallet records for support and reconciliation;
- testing timeouts, retries, callbacks, and uncertain transaction states.
Project onboarding maps the required content, currencies, languages, regions, credentials, and environment configuration into the implementation plan.
- Product and platform owners assessing the integration scope.
- Engineering leads mapping the API to an existing player and wallet architecture.
- Operations teams preparing record lookup, reconciliation, and incident handling.
- Delivery teams defining test cases, ownership, acceptance, and launch readiness.
The current public V5.0.0 surface contains 17 endpoints in four functional groups:
| Area | Purpose | Public endpoint count |
|---|---|---|
| Game catalog and sessions | Discover content, create a game session, and end a player session | 5 |
| Single-wallet callbacks | Coordinate balance, player, bet, settlement, and cancellation events | 5 |
| Transfer wallet | Deposit, withdraw, query balance, inspect transactions, and recover funds | 5 |
| Records and merchant | Query game records and merchant configuration | 2 |
See Public API surface for the endpoint capabilities and their integration purpose. The public website also provides the signing method, representative fields, and redacted examples for technical evaluation. The exact paths for the higher-risk fund-recovery and merchant-configuration operations remain in the controlled implementation package, together with the real Base URL, credentials, complete field constraints, final callback list, and production configuration. These public materials are not the complete production protocol.
- Define the first content, currency, language, and market scope.
- Map the existing player identity, session, wallet, and ledger responsibilities.
- Choose the wallet model based on the current architecture.
- Agree on request identity, retry, timeout, and reconciliation rules.
- Validate the shortest game-launch and wallet path in a test environment.
- Exercise failure and recovery scenarios before production approval.
The integration workflow expands these stages and names the evidence expected at each gate.
- About AG — company positioning, mission, experience, and operating principles.
- Business overview — the services, customers, value, and engagement model.
- Global coverage — the published list of 35 supported countries and regions.
- Game providers — all 11 provider names and their place in the unified API flow.
- Complete game catalog — 1,194 named games mapped to their providers with available English and Chinese names.
- Public API surface — the 17 public capabilities grouped by responsibility, with two higher-risk paths withheld.
- Single wallet and transfer wallet — how the two models change ownership and testing.
- Integration workflow — a bounded path from discovery to launch review.
- Reliability and reconciliation — idempotency, retries, callbacks, and evidence.
- Integration checklist — questions and acceptance cases to prepare before development.
- Frequently asked questions — concise answers to common technical and project questions.
Keep API keys, merchant codes, secrets, allowlists, production hosts, callback hosts, player data, and real transaction records in the designated private technical channel. Signing keys belong only in a controlled server environment, never in browser code, client packages, logs, tickets, chat, or public issues. Public examples use placeholders.
Before production, confirm and test timestamp and nonce replay protection, merchant-level authorization, rate and transaction limits, idempotency, uncertain-result reconciliation, and redacted operational logging in the final project protocol. This public guide does not state that a server has already enabled those controls.
See Security policy before reporting a possible exposure.
- AG official website
- AG Game API documentation
- Slots API overview
- Supported countries and regions
- Chinese guide
During onboarding, AG and the platform team map the required providers, titles, currencies, languages, wallet mode, and regions into a confirmed delivery plan and technical test scope.