This guide provides UK engineers and platforms the specifications necessary to integrate the Balloon Boom Slot game https://balloonboom.net/. You’ll see the API interfaces, payload formats, and configuration options in this document. Following this guide will let you add the game to your iGaming website, comply with UK regulations, and offer your users a flawless gaming experience.
Webhook URLs and Webhook Configuration
You need to set up callback URLs (webhooks) on your server for background updates and enhanced security. The most important one is for balance changes. It offers you a secondary confirmation of any monetary transfer. Our API will POST a signed request to your endpoint, and you must respond with a 200 OK.
Other webhooks can notify you about promotion triggers, session closures, or system alerts. Your callback endpoint must be reliable, rapid, and must check the signature on every incoming message. If you don’t answer, game processes may stall and the player will observe.
Slot Features and Special Rounds
Balloon Boom Slot includes various features like free spins, bonus rounds, and cascading reels. The API manages all functions for these. If a special round begins, the API response will contain a `feature_type` marker and all information the game client requires to show it properly.
For dynamic bonus games, the API monitors the condition. Your backend just sends the gamer’s decisions back, and the API determines the payouts. This approach keeps the complex game logic on our protected servers. It makes your integration simpler and guarantees the game functions as designed.
Handling Cascading Victories and Bonus Spins
With avalanche reels, one bet can lead to various wins in succession. The API aggregates these into a single `bet` response to reduce latency. The response has an array named `cascade_steps`. Each step details the win for that cascade. Total them to calculate the total win, and adjust the gamer’s balance with that total amount.
Getting Started to the Balloon Boom Slot API
The Balloon Boom Slot API acts as a RESTful connection for server-to-server talk. It lets your platform handle game gaming sessions, manage money moves, and retrieve game results securely. It is designed to cope with the heavy load of the UK market. Installation is easy, so you can launch the game swiftly without losing control on the player’s path or your own back-end systems.
The API functions built on a few key concepts. Critical API calls are safe to repeat, so repeated requests are harmless. Error management is straightforward, and the stateless architecture maintains dependability, even during network interruptions. All API requests requires an API key for verification, and all sensitive information is encrypted. This meets the security compliance the UK Gambling Commission demands.
Payment Handling: Wagering and Settlements
The main money loop is basic: put a bet, obtain a result. You hit the `/bet` endpoint with the `session_token` and the exact wager amount. The API checks 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 credited to the player’s balance on your system right away. This happens either through a callback or immediately in the response, based on how you integrated. The API offers you a full win breakdown: the multiplier, the winning lines, and the total. Every single transaction possesses its own ID so you can align everything up later.
- Bet Placement: Call `/bet` with the token and amount. Ensure the player has enough money first.
- Result Processing: The API sends 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: Store the transaction ID, bet amount, win amount, and net change in your own records.
Error Handling and HTTP Codes
The API employs standard HTTP status codes. A `200 OK` means success. `4xx` codes indicate you sent something incorrect, like bad data or a bet with no funds. `5xx` codes indicate something went wrong on our server. Every error response includes a code for your systems and a message for your developers.
You’ll see errors for invalid API keys (`401 Unauthorized`), bets on dead sessions (`410 Gone`), or our server being down (`503 Service Unavailable`). Your code should handle these smoothly, telling the user something’s up without revealing technical secrets. For `5xx` errors, it’s advisable to retry the request with a waiting period that grows longer each time.
Launching Checklist
Moving to production needs a thorough verification. Change all your API calls from the staging URL to the production URL. Set up 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).
Verify 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). Verify that your logging systems are catching all API calls and errors. To finish, 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, keep an eye on it. Watch the API response times, error rates, and whether transactions finish. We have a status dashboard for our services. For help, UK developers can use a dedicated technical support line. Our SLAs specify our uptime promises and how fast we’ll respond if something breaks.
Concluding Steps
This documentation covers what you need to integrate the Balloon Boom Slot for your UK players. Adhere to the authentication, session, and money protocols described here to create a secure and fair game experience. Checking thoroughly in the staging sandbox and ticking off the production checklist are your last tasks before a solid, reliable launch.
API Security and Safeguarding
You must have a specific API key to access the Balloon Boom Slot API. We issue you this key when you get started. Place it in the header of every HTTP request you submit. For money actions, like moving funds, the API also employs HMAC request signing. This extra step makes sure nothing gets modified on the way.
Safe Communication Protocols
You have to connect using TLS 1.2 or a later version. The API offers perfect forward secrecy. Your job is to maintain those API keys private and update them now and then. This is a core part of running a secure service in the UK.
Signature Generation Methodology
For the financial endpoints, you generate a signature with a shared secret. The signature encodes together the request timestamp, a nonce, and the full request body. Our server checks this signature to ensure the request is genuine and unaltered. We reject any request with a timestamp older than five minutes, which prevents replay attacks.
Game Setup 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 chosen bet settings. The API delivers a unique `session_token` and a URL for the game itself. You utilise that token for every following action in that particular 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 resume to the same game within a set time. This keeps things fair and stops players getting annoyed. We log all session data, which you’ll want for UK compliance audits.
User 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`) controls the language and how currency looks. The `currency_code` (for example, GBP) must be the matching the player’s wallet currency. The API verifies the bet limits against both the game’s own rules and any extra limits you submit.
Staging and Development Environment
Avoid going directly live. Use our staging environment first. This sandbox mirrors the real API but operates with pretend money. No real cash changes hands. We provide separate staging API keys so you can simulate the whole player journey, testing wins, losses, and unusual scenarios.
In staging, you can trigger specific game events. You can initiate a bonus round or a jackpot to check how your platform reacts. This is the ideal way to validate your handling of game states and financial tracking. We provide full test scripts and a simulator dashboard to all UK partners.
UKGC Compliance Testing
The staging tools let you test 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 makes sure your live setup will meet UKGC scrutiny.