Τελευταία Νέα

This document offers UK developers and providers the technical details required to add the Balloonboomslot game. You’ll find the API endpoints, payload formats, and configuration options in this document. Following this guide allows you to integrate the game to your iGaming platform, comply with UK rules, and offer your customers a seamless experience.

Last Steps

This documentation details what you need to set up 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. Checking thoroughly in the staging sandbox and ticking off the production checklist are your last tasks before a robust, reliable launch.

Callback endpoints and Webhook Settings

You must configure callback URLs (webhooks) on your server for asynchronous updates and extra security. The key one is for balance updates. It provides you with a secondary confirmation of any money transaction. Our API will POST a signed payload to your endpoint, and you must answer with a 200 OK.

Other webhooks can tell you about promo triggers, session terminations, or system notifications. Your callback endpoint must be reliable, fast, and must check the signature on every incoming message. If you don’t answer, game processes could stall and the player will notice.

Error Processing and Status Codes

The API uses standard HTTP status codes. A `200 OK` means success. `4xx` codes signal you submitted something incorrect, like bad data or a bet with no funds. `5xx` codes mean something went wrong on our server. Every error response contains 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, telling the user something’s up without revealing technical secrets. For `5xx` errors, it’s wise to retry the request with a waiting period that becomes longer each time.

Payment Handling: Wagering and Settlements

The main money loop is simple: put a bet, receive a result. You call 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 rotates the reels. The response comes back with the full result, including any win.

Wins are added to the player’s balance on your system right away. This happens either through a callback or straight in the response, based on how you set it up. 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: Invoke `/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 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.

Sandbox and Development Environment

Don’t go straight to live. Use our staging environment first. This sandbox copies the real API but operates with pretend money. No real cash changes hands. You’ll receive separate staging API keys so you can test the whole player journey, verifying wins, losses, and weird scenarios.

In staging, you can force specific game events. You can initiate a bonus round or a jackpot to observe how your platform handles it. This is the optimal way to validate your handling of game states and financial tracking. We offer 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 ensure that game history and transaction logs are logged properly for regulatory reports. This step guarantees your live setup will meet UKGC scrutiny.

Overview to the Balloon Boom Slot API

The Balloon Boom Slot API is a RESTful connection for server-to-server communication. It lets your platform handle game gaming sessions, process money payment actions, and retrieve game results reliably. It’s built to handle the heavy load of the UK gaming market. Installation is simple, so you can go live with the game quickly without losing control on the player journey or your own backend systems.

The API works built on a few key concepts. Critical API calls are designed to be idempotent, so duplicate calls are harmless. Error management is explicit, and the stateless architecture ensures reliability, even when network issues occur. Each API call demands an API key for authorization, and all private data is encrypted. This meets the security standards the UK Gambling Commission expects.

Game Setup and Session Control

The process begins 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 use that token for every subsequent action in that particular game round.

The session system handles timeouts, dropouts, and games left hanging. The API includes a resume function. If a player gets disconnected, they can come back to the same game within a set time. This ensures equity and prevents players getting annoyed. We log all session data, which you’ll need for UK compliance audits.

Player and Currency Setup

When you start a game, you need to provide 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 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 provide.

API Authentication and Safeguarding

You must have a specific API key to invoke the Balloon Boom Slot API. We provide you this key when you start. Put it in the header of every HTTP request you send. For money operations, like moving funds, the API also uses HMAC request signing. This extra step makes sure nothing gets altered on the way.

Secure Communication Protocols

You have to connect using TLS 1.2 or a newer version. The API provides perfect forward secrecy. Your task is to hold those API keys private and rotate 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 build a signature with a shared secret. The signature combines together the request timestamp, a nonce, and the full request body. Our server checks this signature to verify the request is real and untouched. We deny any request with a timestamp older than five minutes, which blocks replay attacks.

Going Live and Production Checklist

Going live needs a thorough verification. Switch 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).

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). Verify that your logging systems are catching all API calls and errors. Finally, brief your support team on how the game works and what to do if a player has a technical question.

Post-Launch Monitoring

Once the game is live, watch it carefully. Track 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.

Game Features and Bonus Rounds

Balloon Boom Slot offers additional features such as free spins, bonus games, and avalanche reels. The API handles the entire logic for these. If a bonus round begins, the API response will include a `feature_type` marker and all the data the game client requires to display it correctly.

For interactive bonus rounds, the API tracks the state. Your server simply forwards the gamer’s selections back, and the API determines the payouts. This design maintains the intricate game mechanics on our protected servers. It makes your implementation easier and ensures the game operates as designed.

Handling Cascading Victories and Re-Spins

With avalanche reels, one bet can lead to several wins in a row. The API aggregates these into a single `bet` response to reduce latency. The response includes an array titled `cascade_steps`. Each step specifies the win for that cascade. Sum them to calculate the total win, and credit the user’s balance with that ending sum.