Introduction
As a game provider, our objective is to deliver exceptional games and experiences to our customers and their players. We would like to see this translate into you integrating our games onto your casino lobby.
This document provides an insight into our API, known as “NG-Connect”. It addresses the key interactions and requirements from both NetGaming and your perspective. It provides coverage over a wide range of services which can be used by you on your websites, game-servers and any other API services.
You are required to follow a standard integration process; however, this document will provide a brief overview on several key functions required of our API. This includes; integration to NG-Connect API, API request details, server-to-server integration, game integration and wallet transactions.
We have a separate integration guide that explains the overall integration spec and also includes all the various tools, currencies and languages that we support.
Glossary
| Terms | Description |
|---|---|
| Operator | Anyone that owns/operates a website/frontend |
| RGS | Remote Game Server (by provider) |
| Provider | NetGaming / Gaming software provider |
| NG-Connect | NetGaming API. Known as RGS-API as well |
| Session ID / Token | Session ID of the player |
| API Key | Unique key provided by provider to each operator |
| Frontend / Site / White label / Platform | Operator’s website on which games are displayed |
| Game Lobby | Area where games are shown on operator’s website |
The following steps will aid in the integration between NetGaming and new operators.
Request and Response
- HTTP Header “Content-Type”: ”application/json”
- Data sent in POST request should be in JSON format.
- All the API responses are in JSON format
Authentication
- Each API user must obtain a unique API key.
- Each request must contain the API key so each API request can be validated.
Server to Server Communication
Server-level communications between provider and operator would be conducted in JSON format and is transmitted over HTTP. The current default allows one request at any one time; however, simultaneous requests are possible if required. By default, all currency values are provided in cents with no decimal values. In exceptional cases, these can be provided in a base currency (Pounds/Euros).
API Requests from operator to Provider
The following examples are some API requests that are currently provided to operators and third parties. This non-exhaustive list is provided as a brief overview. The number and type of requests can increase, as per an operator's requirements.