Tom Horn Gaming API: 243 Crystal Fruits and the rest of the catalogue in one integration

Tom Horn Gaming, briefly

Tom Horn Gaming is a mid-sized European slot developer. It started in Bratislava under the name Tom Horn Enterprise and later moved its registered head office to Valletta, Malta, where it operates today.

The studio's output is centred on video slots with clear themes: fruit machines reworked with modern ways-to-win, candy-style games and book slots. Its name is less famous than the largest studios, but its strongest titles have a steady audience, which makes it a sensible addition to a lobby that wants depth beyond the obvious brands.

243 ways, explained for the lobby team

A 243-ways slot pays for matching symbols on adjacent reels from left to right, wherever they sit on each reel, instead of along fixed paylines. On a five-reel, three-row grid that gives 3 x 3 x 3 x 3 x 3 = 243 possible combinations per spin.

For players, that means more frequent small wins and a less rigid feel than a 10 or 20-line game. It is the core of Tom Horn's most requested series.

• 243 Crystal Fruits: the studio's signature fruit slot, bright and quick, with the 243-ways engine at its heart.
• 243 Crystal Fruits Deluxe and 243 Crystal Fruits Reversed: follow-ups that keep the formula and change the presentation, so fans can move between them.
• Sweet Crush: a candy-themed game for players who like colourful, casual sessions.
• Frutopia: another fruit-based title that sits well next to the Crystal Fruits series.
• Book of Spells: an expanding-symbol book slot for players who want a higher-volatility feature.

The integration, from keys to first spin

Getting a Tom Horn Gaming title live takes the same four moves as any other studio. You authenticate every POST with api_login and api_password and choose the operation with the method field.

1. Request access on /#signup; after approval your keys and salt_key appear in the operator backend.
2. Call getProviderList and getGameList to load Tom Horn's titles with their id_hash, game_type and image.
3. Create each customer once with createPlayer, picking the currency that customer will keep.
4. Launch with getGame: gameid is the id_hash, plus lang, currency, device, country and homeurl. Put the returned URL in an iframe.

On the money side, your endpoint receives signed GET calls for balance, debit and credit. The docs page lists every parameter and response. In short: amounts are integers in minor units (0.25 arrives as 25); call_id is the transaction's unique key to deduplicate on; round_id ties movements together; game_id equals the id_hash byte for byte.

Edge cases worth testing before launch

Three situations deserve a test run, and none of them is specific to Tom Horn; they are simply where wallets tend to fail.

• Credits without a debit. Free spins in Book of Spells and other features pay out without a new stake. Accept the credit; the type field is informational only.
• Retries. If a call reaches you twice, the second must return the stored result and move no money, thanks to the call_id key.
• Rollbacks. A call carrying rb=1 cancels a previous movement; apply it once.

Reply with HTTP 200 in all cases and set the error field: 0 for success, 1 if the stake exceeds the balance (return that balance), 2 for an invalid signature, an unknown player or a processing issue. The signature is md5(timestamp + salt_key), valid for 30 seconds.

Audiences and currencies

Tom Horn Gaming's fruit-led catalogue fits Central and Eastern European players, Latin American lobbies and markets where classic slots dominate. You set each player's currency at createPlayer and it stays fixed.

Native options that match these audiences include EUR, CZK, PLN, HUF, RON, BGN, TRY, RUB, BRL, MXN, ARS, INR, BDT and ZAR. Where your players use a different currency, your account can run in USD or EUR while your platform converts; tell us which one you need.

Why a studio like Tom Horn belongs in an aggregated lobby

A mid-sized studio rarely justifies its own integration project, but it adds real variety to a lobby. Taking it through a casino game aggregator API means the cost of adding Tom Horn Gaming is a click in your catalogue, not a sprint for your developers.

• Casino games, live dealer content and a sportsbook share one wallet and one integration.
• Your prepaid credit is visible live in the backend, with alerts when it runs low.
• Reports update in real time: bets, wins, RTP% and GGR, sliced by game, player and period.
• Multi-brand accounts: every website keeps its own keys, callback and default currency.
• 24/7 help from engineers on Telegram @mentionso or [email protected].

Catalogues and currency options evolve all the time; getProviderList and getGameList always hold the current picture. To see how studios are organised across the platform, read our game aggregator API overview or browse fellow European studios such as Endorphina.

Tom Horn Gaming: operator questions

Sources and last update

Company origin, head office and title names were checked on Tom Horn Gaming's own pages and in industry directories; we left out the founding year because published sources disagree.

• Tom Horn Gaming website and game pages, September 2026
• Industry directory profiles of Tom Horn Gaming (origin in Bratislava, head office in Malta), September 2026
• SoftAggregator docs.html, September 2026

Last reviewed: 24 September 2026.

Explore more