Oi, como podemos ajudar?
UK programmers and providers who want to include the Book of Dead slot to their platforms need solid API documentation to commence https://slotbookof.com/dead/. This guide covers the Book of Dead slot API. It walks through the endpoints, data formats, and how to implement it, all with the UK’s regulated market in mind. You’ll find out about authentication, running spins, and handling the game’s iconic Expanding Symbol mechanic. The objective is a trustworthy, legally sound implementation.
The Book of Dead slot API is a RESTful service that uses JSON for sending and receiving data. Developed for high uptime, it holds players engaged even during peak periods like major football matches. The design divides the game logic server from the client-side display. This division assures that results, like reel stops and bonus triggers, are arbitrary and processed securely on the backend.
In a typical setup, your platform is the client. It starts sessions and sends player actions. An API gateway receives these requests and routes them to the appropriate game service. For UK operators, this system facilitates the audit trails and data segregation the Gambling Commission requires. Comprehending this sequence helps with debugging and incorporating custom features like tournaments or special promotions.
The API is stateless. Every request must carry its own authentication and context. This strategy promotes scalability and dependability, enabling the service to manage traffic spikes. To ensure things smooth for users, even with network hiccups, you should include retry logic and connection pooling on your end.
Security comes first. The Book of Dead API uses OAuth 2.0 client credentials for authentication. You require a unique `client_id` and `client_secret` from the provider. All transmission happens over HTTPS, with a bearer token placed in the `Authorization` header. Since this token runs out, your code must update it automatically to avoid breaking a player’s session.
To start a game session, send a POST request to `/session/start`. The payload requires the player’s unique ID (linked to your system), their currency (GBP), and language preference. For UK compliance, you must also include the player’s current session ID from your responsible gambling tools. This lets the game link with timeout and limit capabilities. The response provides you a `game_session_token` for all further requests.
We use strict IP whitelisting for server-to-server calls from UK operators. Also, every spin and financial transaction gets a digital signature. Your integration must check these signatures with our public key to verify data hasn’t been altered. This step is essential for legal UK operation and protects both you and the player from tampering.
The primary endpoint for play is `/game/spin`. A POST request here triggers a single spin at the player’s picked stake. The request must include the `game_session_token`, the `stake` in GBP, and an elective `feature_buy` flag if you offer that. Your system should confirm the player has adequate funds before calling the API, since the API does not handle wallet balances.
The spin response is a detailed JSON object. It contains a `reel_stops` array displaying each reel’s position and a `symbols_matrix` for your client to render. The `winning_lines` array describes any payline wins, showing the line number, symbol, and payout. Critically, it tells you if the Free Spins bonus round started, which happens when three or more Book scatter symbols show up anywhere.
For the UK market, the response contains required compliance fields. These are a `spin_timestamp` in UTC, a specific `round_id` for audits, and the `total_payout`. You are required to store this data permanently for UKGC reporting and any customer disputes. A recommended approach is to log it in real-time as soon as you get the response, so nothing is lost.
When the Free Spins round starts, a distinct series begins. The original base game spin response marks the trigger. Your client then sends `/bonus/initiate` with the `round_id` from that spin. This provides the bonus information: how many free spins were given and, most crucially, the randomly selected `expanding_symbol` for this game.
The Expanding Symbol is what renders Book of Dead thrilling. During free spins, one normal symbol converts into an expanding wild. If this symbol hits, it extends to fill the full reel, generating bigger wins. The API response for each free spin explicitly says if an spread happened and the win rate that followed. Your visual should show this spread clearly to align with the game’s style and what players anticipate.
You execute each free spin with a call to `/bonus/spin`. The series goes on until all granted spins are consumed. The API tracks the bonus round state, so you only need to send the `bonus_round_id`. Wins add up, and the aggregate is given at the end. Your user interface should show the count of free spins left and the active expanding symbol, maintaining the player informed.
Financial accuracy is crucial. The Book of Dead API does not handle real money. It only determines win amounts. Your platform must deduct the stake before invoking the spin endpoint, then apply the winnings after you get and confirm the result. This demands solid, atomic transaction logic on your backend to avoid race conditions or balance errors.
All money values in the API are in GBP, with two decimal places. The `payout` value in the response is the net win for that spin (the total win minus the stake). You allocate this amount to the player’s balance. UK operators also need to record `total_stake` and `total_wins` per player session to determine Gross Gambling Yield for regulatory reports.
We offer a `/transactions/history` endpoint for reconciliation. You can query it with a date range or a specific `round_id` to obtain a signed record of all transactions. UK licensees typically perform a daily reconciliation with this data. It checks that your financial records line up with the provider’s logs, creating a clear audit trail.
Proper error handling ensures stability. The API utilizes standard HTTP status codes along with a specific `error_code` and `message` in the response body. Common errors are `INSUFFICIENT_BALANCE` (which you should trap before the request), `SESSION_EXPIRED`, and `BET_LIMIT_EXCEEDED`. Your code must handle these gracefully, perhaps by directing the player to a deposit page or clarifying a limit breach, following UK responsible gambling rules.
UK-specific compliance errors demand attention. If a player’s self-exclusion or timeout triggers during a game, the API might send a `PLAYER_SUSPENDED` error. Your integration must halt the game session right away and move the player to a secure, non-gambling part of your site. Documenting these events for your compliance team is required. The same applies for age verification failures; gameplay must cease immediately.
Consider using a circuit breaker pattern for API calls. If you encounter several timeouts or server errors (5xx statuses) in a row, your system should stop trying and handle failure smoothly, maybe showing a maintenance message. This improves the user experience and avoids your servers from overloading. Set up monitoring to alert your tech team if 4xx or 5xx error rates rise, so they can look into quickly.
Never go live without extensive testing in the sandbox. This environment emulates the live API but uses test money and won’t impact real finances. You’ll get sandbox-only `client_id` and `client_secret` credentials. It enables you to simulate the whole player experience, from signing up and depositing to playing and withdrawing, so you can address any edge cases.
UK developers should concentrate on key test scenarios. Model the bonus round trigger often to check the Expanding Symbol animation works. Test large wins to confirm your balance updates and any manual review processes operate. You must also test how your integration works with responsible gambling tools, like sending a timeout signal to verify gameplay stops properly. This is a regulatory requirement.
The sandbox also includes tools to force specific outcomes, like triggering a bonus or a losing spin. This is very useful for building and testing features like game history logs, bonus buy options, and your own promotional messages. Build a complete automated test suite for these scenarios. Run it frequently, especially before you update your platform or when a new API version is released.
