Casino API integration handbook

Start with your integration decision

Building an operator backend? Follow the modules below. Evaluating a supplied player website? Compare the turnkey website scope with your own delivery responsibilities. Game studios should use the supplier onboarding enquiry; these operator documents are not a supplier API specification.

Eight modules from credentials to production

Each module links to the maintained reference rather than a duplicate article. The outcome describes what your implementation should demonstrate, not access granted by reading the guide.

1. Backend authentication

   Keep X-API-Key on your backend; identify the scopes and egress IPs each service needs.

2. Catalogue and currency discovery

   Select an enabled play currency and store the exact returned game identifier.

3. Demo launches

   Check trial support and both HTTP and application success without reserving player funds.

4. Production game sessions

   Persist the launch request and idempotency key, reserve starting funds and validate return origins.

5. Signed wallet settlements

   Verify exact body bytes and durably accept each serial_number once, including concurrent delivery.

6. Idempotency and reconciliation

   Distinguish rejected, pending and unknown operations before changing a wallet reservation.

7. Activation and GGR funding

   Keep activation purchases, player funds and the workspace GGR wallet separate.

8. PHP, Node.js, Java and Postman

   Adapt backend examples and private test requests without exporting credentials or automating unsafe retries.

Finish with evidence, not just a successful demo

Keep a test record linking a catalogue choice, launch request, reservation, callback serial and reconciliation decision. Exercise invalid signatures, concurrent duplicates, delayed events and an unknown launch outcome in a controlled environment. A demo cannot prove that a production wallet is correct.

Complete the sandbox-to-production checklist, confirm your provider and currency entitlements, and agree who handles unknown outcomes before opening production access.

Use the catalogue and financial tools together

The provider directory and integration guides describe current catalogue records, not guaranteed titles or market permissions. The GGR calculator separates provider/currency groups, while pricing explains activation and published rates.

Published by Aggregator Network using the current API reference. No independent technical certification is claimed. Send corrections or scope questions through the integration contact, without credentials or temporary launch URLs.