Book of Dead Game API Documentation for UK Developers

UK programmers and operators who want to integrate the Book of Dead slot to their sites need comprehensive API documentation to commence. This guide describes the Book of Dead slot API. It outlines the routes, data types, and how to implement it, all with the UK’s regulated market in mind. You’ll find out about authorization, simulating spins, and managing the game’s famous Expanding Symbol feature. The objective is a dependable, legally valid implementation.

Grasping the Book of Dead API Structure

The Book of Dead slot API is a RESTful service that uses JSON for transmitting and accepting data. Designed for high availability, it holds players involved even during heavy periods like major football matches. The design divides the game logic server from the client-side presentation. This separation guarantees that findings, like reel stops and bonus triggers, are random and handled securely on the backend.

In a standard setup, your platform is the client. It begins sessions and transmits player actions. An API gateway takes these requests and routes them to the appropriate game service. For UK operators, this structure enables the audit trails and data separation the Gambling Commission mandates. Understanding this sequence helps with debugging and incorporating custom features like tournaments or special promotions.

The API is stateless. Every request must contain its own authentication and context. This strategy supports scalability and reliability, enabling the service to manage traffic spikes. To maintain things smooth for users, even with network problems, you should add retry logic and connection pooling on your end.

Security and Secure Session Setup

Protection comes first. The Book of Dead API uses OAuth 2.0 client credentials for authentication. You need a unique `client_id` and `client_secret` from the provider. All communication happens over HTTPS, with a bearer token placed in the `Authorization` header. Since this token becomes invalid, your code must refresh it automatically to avoid disrupting 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 allows the game link with timeout and limit features. The response returns you a `game_session_token` for all further communications.

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 verify these signatures with our public key to ensure data hasn’t been modified. This step is essential for legal UK operation and protects both you and the player from interference.

Core Gameplay Endpoints: Spin and Payout

The key endpoint for play is `/game/spin` https://slotbookof.com/dead/. 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 optional `feature_buy` flag if you provide that. Your system needs to verify the player has enough funds before calling the API, because the API does not process wallet balances.

The spin response returns a detailed JSON object. It includes a `reel_stops` array indicating each reel’s position and a `symbols_matrix` for your client to display. The `winning_lines` array details any payline wins, specifying the line number, symbol, and payout. Importantly, it tells you if the Free Spins bonus round started, which occurs when three or more Book scatter symbols land anywhere.

For the UK market, the response includes required compliance fields. These are a `spin_timestamp` in UTC, a unique `round_id` for audits, and the `total_payout`. You must store this data indefinitely for UKGC reporting and any customer disputes. A good practice is to log it synchronously as soon as you obtain the response, so nothing is lost.

Managing the Free Spins Feature and Enlarging Symbol

When the Free Spins bonus activates, a distinct process commences. The first base game spin reply signals the start. Your client then requests `/bonus/initiate` with the `round_id` from that spin. This returns the bonus information: how many free spins were granted and, most importantly, the randomly picked `expanding_symbol` for this round.

The Expanding Symbol is what turns Book of Dead thrilling. During free spins, one normal symbol changes into an expanding wild. If this symbol hits, it extends to fill the whole reel, generating bigger wins. The API reply for each free spin explicitly states if an enlargement happened and the win multiplier that ensued. Your graphic should demonstrate this expansion clearly to align with the game’s design and what players expect.

You execute each free spin with a request to `/bonus/spin`. The run goes on until all awarded spins are exhausted. The API monitors the bonus round condition, so you only need to send the `bonus_round_id`. Wins build up, and the total is granted at the end. Your user display should display the number of free spins left and the live expanding symbol, ensuring the player informed.

Payment Integration and Transaction Reporting

Precision in finances is critical. The Book of Dead API does not touch real money. It only determines win amounts. Your platform must subtract the stake before calling the spin endpoint, then credit the winnings after you receive and validate 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 deposit this amount to the player’s balance. UK operators also need to record `total_stake` and `total_wins` per player session to work out Gross Gambling Yield for regulatory reports.

We supply a `/transactions/history` endpoint for reconciliation. You can fetch it with a date range or a specific `round_id` to retrieve a signed record of all transactions. UK licensees typically conduct a daily reconciliation with this data. It verifies that your financial records match with the provider’s logs, establishing a clear audit trail.

Error Processing and Regulatory Compliance for the UK Market

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 handle before the request), `SESSION_EXPIRED`, and `BET_LIMIT_EXCEEDED`. Your code must handle these seamlessly, perhaps by redirecting the player to a deposit page or describing a limit breach, following UK responsible gambling rules.

UK-specific compliance errors need attention. If a player’s self-exclusion or timeout activates during a game, the API might return a `PLAYER_SUSPENDED` error. Your integration must terminate the game session right away and take the player to a safe, non-gambling part of your site. Documenting these events for your compliance team is mandatory. The same holds true for age verification failures; gameplay must stop immediately.

Consider using a circuit breaker pattern for API calls. If you see several timeouts or server errors (5xx statuses) in a row, your system should cease attempts and fail gracefully, maybe presenting a maintenance message. This boosts the user experience and prevents your servers from overloading. Set up monitoring to notify your tech team if 4xx or 5xx error rates increase, so they can diagnose quickly.

Trialing and Modeling in a Sandbox Environment

Never go live without thorough testing in the sandbox. This environment reflects 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 fix any edge cases.

UK developers should concentrate on key test scenarios. Simulate 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 function. 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 legal requirement.

The sandbox also includes tools to force specific outcomes, like activating 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 consistently, especially before you update your platform or when a new API version is released.