API Documentation
Integration guide for signed game launches, the game catalog, and internally processed provider callbacks.
https://igamingapi.live/v1/launch
Every launch requires HMAC SHA-256 authentication, an active 32-character catalog UID enabled for your client, a canonical two-decimal balance, and INR currency.
Quick Start
Use your client API key and secret with the signed launch endpoint.
Sign every request; IP allowlisting is an additional restriction, not a replacement for HMAC.
Launch API
Start a game using its exact 32-character provider UID. Game codes are not launch identifiers.
Launch requests use POST and currently support INR only.
Callback API
HUIDU's encrypted callbacks are authenticated, session-matched, and processed by this service.
Serial-number idempotency prevents duplicate wallet and GGR effects; an optional client callback receives forwarded event data.
Integration Checklist
- Token and secret generated in operator console
- POST HMAC launch tested with a valid catalog UID and INR balance
- Provider callback credentials and callback URL configured
- Apply the callback event-ledger SQL before the first provider callback
Need Technical Help?
Our technical engineers can review your integration payload and test endpoints with you prior to go-live.
Request Integration Support