This manual gives UK developers and platforms the tech specs needed to add the balloon boom slot deposit and withdrawal Boom Slot game. You’ll find the API interfaces, data structures, and settings in this document. By following these steps allows you to deploy the game to your iGaming site, comply with UK regulations, and give your players a seamless gaming experience.
Going Live and Production Checklist
Moving to production needs a thorough verification. Change all your API calls from the staging URL to the production URL. Get your live API keys in place, stored securely. Do a final end-to-end test with real money, even if it’s just a few pence (a «penny drop» test).
Make sure your callback URLs are live on the public internet, using HTTPS, and that your firewall permits traffic from our production servers (we’ll give you the IP list). Double-check that your logging systems are recording all API calls and errors. Finally, prepare your support team on how the game works and what to do if a player has a technical question.
Launch Follow-Up
Once the game is live, watch it carefully. Track the API response times, error rates, and whether transactions complete. We offer a status dashboard for our services. For help, UK developers can use a dedicated technical support line. Our SLAs outline our uptime promises and how fast we’ll respond if something breaks.
Overview to the Balloon Boom Slot API
The Balloon Boom Slot API acts as a RESTful interface for server-to-server communication. It allows your system administer game sessions, handle money financial transactions, and fetch game results securely. It’s built to manage the heavy load of the UK iGaming market. Configuration is simple, enabling you to launch the game rapidly without losing grip on the player’s path or your own server infrastructure.
The API works built on a few key concepts. Key requests are idempotent, so duplicate calls are harmless. Error handling is straightforward, and the stateless design maintains dependability, even during network interruptions. Every API request demands an API key for authorization, and all private data gets encrypted. This matches the security compliance the UK Gambling Commission requires.
Slot Features and Special Rounds
Balloon Boom Slot has extra features like free spins, bonus games, and tumbling reels. The API controls the entire logic for these. If a special round begins, the API response will contain a `feature_type` indicator and all information the game client needs to show it properly.
For dynamic bonus features, the API monitors the condition. Your server just sends the user’s decisions back, and the API calculates the prizes. This design maintains the intricate game mechanics on our safe servers. It makes your integration simpler and guarantees the game functions as intended.
Handling Avalanche Wins and Respins
With avalanche reels, one bet can produce multiple wins in a row. The API aggregates these into a single `bet` response to save time. The response contains an array named `cascade_steps`. Each step provides details of the win for that cascade. Total them to get the total payout, and credit the user’s balance with that final sum.
API Security and Protection
You must have a unique API key to invoke the Balloon Boom Slot API. We give you this key when you get started. Include it in the header of every HTTP request you send. For money transactions, like moving funds, the API also uses HMAC request signing. This extra step ensures nothing gets altered on the way.
Safe Communication Protocols
You must connect using TLS 1.2 or a newer version. The API provides perfect forward secrecy. Your task is to maintain those API keys confidential and change them now and then. This is a core part of operating a secure service in the UK.
Signature Generation Methodology
For the financial endpoints, you create a signature with a shared secret. The signature combines together the request timestamp, a nonce, and the full request body. Our server verifies this signature to verify the request is real and unmodified. We reject any request with a timestamp older than five minutes, which prevents replay attacks.
Financial Transactions: Gambling and Settlements
The main money loop is simple: put a bet, obtain a result. You invoke the `/bet` endpoint with the `session_token` and the exact wager amount. The API verifies the bet, removes the money from the player’s credit (which you manage), and spins the reels. The response arrives with the full result, covering any win.
Wins are applied to the player’s balance on your system right away. This takes place either through a callback or immediately in the response, depending on how you connected. The API provides you a full win breakdown: the multiplier, the winning lines, and the total. Every single transaction has its own ID so you can align everything up later.
- Bet Placement: Invoke `/bet` with the token and amount. Check the player has enough money first.
- Result Processing: The API delivers back the game outcome and any win amount in one step.
- Balance Update: Your platform adjusts the player’s cash balance right away. Use the net change (win minus bet).
- Transaction Logging: Save the transaction ID, bet amount, win amount, and net change in your own records.
Sandbox and Development Environment
Avoid going directly live. Start with our staging environment. This sandbox mirrors the real API but works with pretend money. No actual money is involved. You’ll receive separate staging API keys so you can run through the whole player journey, verifying wins, losses, and edge scenarios.
In staging, you can simulate specific game events. You can activate a bonus round or a jackpot to see how your platform reacts. This is the ideal way to check your handling of game states and financial tracking. We provide full test scripts and a simulator dashboard to all UK partners.
UKGC Compliance Simulation
The staging tools let you verify UK compliance features. You can test our reality check prompts and time-out functions. You can also verify that game history and transaction logs are stored properly for regulatory reports. This step ensures your live setup will satisfy UKGC scrutiny.
Game Initialisation and Session Management
It all starts with initiating a player session. Your server calls the `/game/init` endpoint with the player’s ID and their preferred bet settings. The API sends back a unique `session_token` and a URL for the game itself. You use that token for every following action in that certain game round.
The session system manages timeouts, dropouts, and games left hanging. The API has a resume function. If a player gets disconnected, they can come back to the same game within a set time. This ensures equity and avoids players getting annoyed. We record all session data, which you’ll require for UK compliance audits.
Gambler and Currency Setup
When you initialise a game, you need to transmit specific details to configure it correctly. The player’s locale (like `en-GB`) determines the language and how currency looks. The `currency_code` (for example, GBP) must be the same as the player’s wallet currency. The API validates the bet limits against each of the game’s own rules and any extra limits you submit.
Webhook URLs and Webhook Configuration
You should establish callback URLs (webhooks) on your server for asynchronous updates and enhanced security. The critical one is for balance updates. It provides you with a second confirmation of any financial transaction. Our API will POST a signed payload to your endpoint, and you must answer with a 200 OK.
Other webhooks can inform you about promotion triggers, session closures, or system alerts. Your callback endpoint must be trustworthy, fast, and must check the signature on every incoming message. If you don’t answer, game processes can stall and the player will observe.
Error Handling and Response Codes
The API utilizes standard HTTP status codes. A `200 OK` signals success. `4xx` codes mean you submitted something invalid, like bad data or a bet with no funds. `5xx` codes indicate something went wrong on our server. Every error response has a code for your systems and a message for your developers.
You’ll find errors for invalid API keys (`401 Unauthorized`), bets on dead sessions (`410 Gone`), or our server being down (`503 Service Unavailable`). Your code needs to handle these cleanly, notifying the user something’s up without revealing technical secrets. For `5xx` errors, it’s smart to retry the request with a waiting period that grows longer each time.
Concluding Steps
This documentation includes what you need to implement the Balloon Boom Slot for your UK players. Stick to the authentication, session, and money protocols described here to establish a secure and fair game experience. Testing thoroughly in the staging sandbox and ticking off the production checklist are your last tasks before a solid, reliable launch.
