02 / API reference
API directory
Find the request contract for each wallet callback and partner API operation.
Requests travel in two directions. Wallet callbacks arrive at endpoints you implement. Partner API requests leave your backend and go to your assigned Wildvolt Operator API base URL.
Wildvolt → your wallet
| Contract | Method and path | Use it to |
|---|---|---|
| Read a balance | POST /player-balance | Report current funds |
| Debit a wager | POST /withdraw | Deduct a bet stake |
| Credit a settlement | POST /deposit | Apply a result or supported credit |
| Credit in batches | POST /deposit-batch | Process multiple credits |
| Reverse a debit | POST /rollback | Reverse a previous withdrawal |
Your backend → Wildvolt
| Contract | Use it to |
|---|---|
| List available games | Retrieve your configured games and instances |
| Look up a bet | Investigate a recorded transaction |
| Find a player's round | Resolve a query using a player and round |
| Issue a free bet | Grant free bets for a game instance |
Protected partner requests require your operator ID and request signature. Use the authentication instructions on the individual endpoint page. For callbacks sent to your wallet, begin with Verify every request.
Authenticate partner requests
The API version is v0.2. Protected requests require both headers:
| Header | Value |
|---|---|
X-Operator-Id | Your registered operator identifier |
X-Signature | The RSA-SHA256 signature, encoded as base64url without padding |
Sign the endpoint-specific data with your operator private key. Wildvolt verifies the signature with the public key registered for your operator. Each request page specifies exactly what to sign.
Wildvolt uses the EU service at https://operators.wildvoltgames.com. Confirm your assigned account and game instances during onboarding. Example hosts are not an access grant.