This document offers UK developers and platforms the tech specs needed to integrate the Balloon Boom Slot game https://balloonboom.net. You will discover the API endpoints, data formats, and configuration options in this document. By following these steps will let you deploy the game to your iGaming platform, comply with UK regulations, and give your players a smooth gaming experience.
Error Management and Response Codes
The API uses standard HTTP status codes. A `200 OK` indicates success. `4xx` codes mean you submitted 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 find 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 gracefully, notifying the user something’s up without revealing technical secrets. For `5xx` errors, it’s advisable to retry the request with a waiting period that becomes longer each time.
API Verification and Protection
You need a specific API key to access the Balloon Boom Slot API. We issue you this key when you begin. Put it in the header of every HTTP request you send. For money operations, like moving funds, the API also utilizes HMAC request signing. This extra step ensures nothing gets modified on the way.
Secure Communication Protocols
You have to connect using TLS 1.2 or a later version. The API provides perfect forward secrecy. Your role is to keep those API keys private and rotate them now and then. This is a basic part of running a secure service in the UK.
Signing Methodology
For the financial endpoints, you create a signature with a shared secret. The signature hashes together the request timestamp, a nonce, and the full request body. Our server verifies this signature to confirm the request is real and unmodified. We reject any request with a timestamp older than five minutes, which prevents replay attacks.
Testing and Testing Environment
Skip the live environment. Use our staging environment first. This sandbox replicates the real API but works with pretend money. Real funds are not used. We provide separate staging API keys so you can run through the whole player journey, verifying wins, losses, and unusual scenarios.
In staging, you can simulate specific game events. You can initiate a bonus round or a jackpot to see how your platform reacts. This is the best way to check your handling of game states and financial tracking. We supply full test scripts and a simulator dashboard to all UK partners.
UKGC Compliance Testing
The staging tools let you check 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 logged properly for regulatory reports. This step ensures your live setup will satisfy UKGC scrutiny.
Going Live and Production Checklist
Moving to production needs a thorough verification. Switch all your API calls from the staging URL to the production URL. Obtain 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 accepts 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, inform 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 provide 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.
Payment Handling: Betting and Settlements
The main money loop is simple: put a bet, get a result. You invoke the `/bet` endpoint with the `session_token` and the exact wager amount. The API checks the bet, takes the money from the player’s credit (which you manage), and spins the reels. The response returns with the full result, containing any win.
Wins are credited to the player’s balance on your system right away. This happens either through a callback or straight 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 carries its own ID so you can align everything up later.
- Bet Placement: Call `/bet` with the token and amount. Verify 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 updates the player’s cash balance immediately. Use the net change (win minus bet).
- Transaction Logging: Store the transaction ID, bet amount, win amount, and net change in your own records.
Concluding Steps
This documentation covers what you need to integrate the Balloon Boom Slot for your UK players. Follow the authentication, session, and money protocols described here to build a secure and fair game experience. Verifying thoroughly in the staging sandbox and ticking off the production checklist are your last tasks before a solid, reliable launch.
Game Initialisation and Session Management
The process begins with launching a player session. Your server requests the `/game/init` endpoint with the player’s ID and their selected bet settings. The API delivers a unique `session_token` and a URL for the game itself. You employ that token for every following action in that certain game round.
The session system deals with timeouts, dropouts, and games left hanging. The API offers a resume function. If a player gets disconnected, they can resume to the same game within a set time. This ensures equity and avoids players getting annoyed. We log all session data, which you’ll require for UK compliance audits.
Player and Currency Setup
When you set up a game, you need to provide specific details to set it up right. The player’s locale (like `en-GB`) controls the language and how currency looks. The `currency_code` (for example, GBP) must be the identical to the player’s wallet currency. The API validates the bet limits against each of the game’s own rules and any extra limits you send.
Getting Started to the Balloon Boom Slot API
The Balloon Boom Slot API is a RESTful interface for server-to-server data exchange. It lets your system handle game sessions, process money financial transactions, and fetch game results safely. It’s constructed to cope with the heavy load of the UK iGaming market. Installation is easy, allowing you to get the game live swiftly while maintaining control on the player’s path or your own server infrastructure.
The API functions based on a few core principles. Important calls are safe to repeat, so repeating them won’t cause problems. Error responses is straightforward, and the stateless architecture keeps things reliable, even if the network hiccups. All API requests needs an API key for authorization, and all private data is encrypted. This complies with the security standards the UK Gambling Commission requires.
Game Attributes and Free Rounds
Balloon Boom Slot has extra features like free spins, bonus rounds, and avalanche reels. The API handles the entire logic for these. If a bonus round triggers, the API response includes a `feature_type` marker and all the data the game client requires to show it properly.
For engaging bonus games, the API monitors the status. Your system just sends the gamer’s selections back, and the API works out the rewards. This approach places the complicated game mechanics on our protected servers. It renders your integration more straightforward and guarantees the game functions as intended.
Handling Cascading Victories and Bonus Spins
With avalanche reels, one bet can lead to multiple wins in succession. The API groups these into a single `bet` response to save time. The response contains an array titled `cascade_steps`. Each step specifies the win for that cascade. Add them all up for the total payout, and update the gamer’s balance with that total amount.
Callback endpoints and Webhook Settings
You must configure callback URLs (webhooks) on your server for async updates and enhanced security. The key one is for balance notifications. It offers you a additional verification of any monetary transfer. Our API will POST a signed payload to your endpoint, and you must answer with a 200 OK.
Other webhooks can inform you about promotional triggers, session closures, or system alerts. Your callback endpoint must be reliable, rapid, and must verify the signature on every incoming request. If you fail to reply, game processes could stall and the player will observe.
