Start Game

Info

The Start Game endpoint is the entry point for launching games through the Tech Fusion platform. This section explains how to initiate game sessions for players.

Overview

The Start Game process is the mechanism by which casino operators launch games for their players. When a player selects a game on the casino’s website or application, the casino makes a request to the Tech Fusion API to generate a unique game URL. This URL is then used to redirect the player to the game, either in an iframe or a new browser tab.

Warning

For Sportsbook products, a different launch process is used. See [Sportsbook Start Game](/appendix-b-sportsbook-start-game/) for details.

Start Game Process Flow

The diagram below illustrates the standard game launch flow:

sequenceDiagram participant Player participant Casino as Casino Operator participant Tech Fusion as Tech Fusion Platform participant Game as Game Provider Player->>Casino: Select Game to Play Casino->>Tech Fusion: Start Game Request Tech Fusion->>Tech Fusion: Validate Parameters Tech Fusion->>Game: Initialize Game Session Game->>Tech Fusion: Session Created Tech Fusion->>Casino: Game URL Response Casino->>Player: Redirect to Game URL Player->>Game: Access Game Interface Note over Player,Game: Player begins gameplay

Game Launch Steps

A player selects a game to play on the casino’s platform
The casino sends a Start Game request to the Tech Fusion API with required parameters
Tech Fusion validates the request and creates a session with the game provider
Tech Fusion returns a redirect URL for the specific game
The casino redirects the player to this URL (via iframe or new tab)
The game loads and the player begins gameplay

API Reference

Endpoint

GET https://{techfusion_domain}/game/

Request Parameters

Parameter	Data type	Required	Description
accountid	String(60) -[0-9a-zA-Z]	Yes	Player’s unique identifier Example: `5179068`
country	String	Yes	Player’s location (ISO 3166-1 alpha-2 code) Examples: `IL`, `UK`, `US`
nogsgameid	Integer	Yes	Tech Fusion game identifier Example: `80102`
nogslang	String	Yes	Interface language (ISO format) Example: `en_US`
nogsmode	String	Yes	Game mode Valid values: `demo`, `real`
nogsoperatorid	String	Yes	Casino’s Tech Fusion ID Example: `11`
nogscurrency	String	Yes	Currency code (ISO 4217) Example: `EUR`
sessionid	String(64)	Yes	Unique session identifier Format: `{nogsoperatorid}_{uuid}` Example: `11_99d71938-c2d9-4844-b950-d598c2es`
homeurl	String(50)	Yes	URL to redirect player after game exit Example: `https://www.casino.com/games`
historyUrl	String(50)	No	URL for player game history (regulatory) Example: `https://www.casino.com/player/history`
license	String	Yes	Gaming jurisdiction Available licenses: `Curacao`, `Malta`, `UK`
is_test_account	Boolean	Yes (in real mode)	Indicates test player status Values: `true` (test player), `false` (real player)
device_type	String	Yes	Player’s device type Valid values: `desktop`, `mobile`
exitUrl	String	No	URL for reality check redirect Example: `https://www.casino.com/responsible-gaming`
rc_url	String	No	Reality check application URL Example: ``
realityCheckElapsed	Integer	No (UKGC requirement)	Minutes elapsed since session start Example: `10`
realityCheckInterval	Integer	No (UKGC requirement)	Minutes between reality checks Example: `15`

Note

All parameters must be URL-encoded in the request.

Example Request

GET https://{techfusion_domain}/game/?accountid=5179068&country=UK&nogsgameid=80102&nogslang=en_US&nogsmode=real&nogsoperatorid=11&nogscurrency=EUR&sessionid=11_99d71938-c2d9-4844-b950-d598c2es&homeurl=https%3A%2F%2Fwww.casino.com%2Fgames&historyUrl=https%3A%2F%2Fwww.casino.com%2Fplayer%2Fhistory&license=UK&is_test_account=false&device_type=desktop&realityCheckElapsed=0&realityCheckInterval=60

Response

Success Response

HTTP/1.1 302 Found
Location: https://game-provider.com/launch/[game-specific-parameters]

When successful, the API responds with a HTTP 302 redirect to the game launch URL. The casino should redirect the player to this URL to start the game session.

Error Response

{
  "errMsg": "error_code",
  "details": "Human-readable error description"
}

Common error codes:

Error Code	Description
invalid_parameter	One or more parameters are invalid or missing
game_unavailable	The requested game is not available
unauthorized	Invalid operator ID or other authentication issue
general_error	An unexpected error occurred

Implementation Guidelines

Browser Integration

Games can be launched in two ways:

Iframe Integration: Embed the game within your casino website

<iframe src="[game_url]" width="100%" height="600px" frameborder="0"></iframe>

New Window/Tab: Open the game in a separate browser window
```
window.open("[game_url]", "_blank");
```

Session Management

Generate a unique session ID for each game launch
Include the operator ID prefix in the session ID
Store the session ID in your system for transaction correlation
In demo mode, use 0 for both sessionid and accountid

Device Compatibility

Specify the correct device_type parameter to ensure proper game rendering
Not all games support both desktop and mobile devices
Test game launches on all target devices before production deployment

Responsible Gaming

For UK Gambling Commission (UKGC) compliance:

Always include realityCheckElapsed and realityCheckInterval parameters
Provide a valid exitUrl for reality check redirects
Set appropriate intervals based on regulatory requirements

Troubleshooting

If you encounter issues with game launches:

Verify all parameters are correctly formatted and URL-encoded
Ensure the nogsoperatorid matches your assigned Tech Fusion ID
Check that the game ID is valid and available for your integration
Confirm the session ID follows the required format
Verify the player’s country is supported by the game provider

For persistent issues, contact Tech Fusion support with the full request URL and any error responses received.

Next Steps

After successfully implementing the Start Game flow, proceed to the Transaction API section to learn how to handle in-game financial transactions.