Darwin

## 🚀 Theneo

Theneo is the quickest, simplest way to generate high-quality, interactive API docs. Just import your API collection and we'll take care of the rest.

**⚠️ Note:** All of the stated endpoints and sections are for demonstration purposes only. Theneo does not manage payments API. Get sales data, itemize payments, push orders to POS, and more.The Orders API provides a one-stop shop for integrating advanced payment functionality. You can itemize payments with custom line items or catalog objects, send orders to real Point of Sale devices to be fulfilled, and more.In addition, the Orders API allows you to look through all of a seller's previous sales and returns itemization data, customer references, and other information from POS or online transactions.

&lt;img src="https://assets.website-files.com/61f7e03934c23c1dcc9c3cd4/6306089ecc13c15fe0a7e006_Main page_2 (with visual studoi code logo) 2.svg" alt="" height="237" width="322">

### Generate API Documentation

- Build interactive API docs
- Tailor you documentation
- Create and launch quickly
- Update easily within seconds
- Built for everyone
    

# Integrations

Import your collections manually or use our integrations to automatically migrate your work from:

- Swagger
- Postman
- Github
    

[  
](https://www.theneo.io/#)

[  
](https://app.theneo.io/signup)

API Reference

🚀 Theneo is the quickest, simplest way to generate high-quality, interactive API docs. Just import your API collection and we'll take care of the rest.

⚠️ Note**:** All of the stated endpoints and sections are for demonstration purposes only. Theneo does not manage payments API. Get sales data, itemize payments, push orders to POS, and more.The Orders API provides a one-stop shop for integrating advanced payment functionality. You can itemize payments with custom line items or catalog objects, send orders to real Point of Sale devices to be fulfilled, and more.In addition, the Orders API allows you to look through all of a seller's previous sales and returns itemization data, customer references, and other information from POS or online transactions.

&lt;img src="https://assets.website-files.com/61f7e03934c23c1dcc9c3cd4/6306089ecc13c15fe0a7e006_Main page_2 (with visual studoi code logo) 2.svg" alt="" height="168" width="200">

### Generate API Documentation

- Build interactive API docs
- Tailor you documentation
- Create and launch quickly
- Update easily within seconds
- Built for everyone
    

# Integrations

Import your collections manually or use our integrations to automatically migrate your work from:

- Swagger
- Postman
- Github

Requests

Open Game

Get Account Details

Get Balance

Creates a new customer for a business.

You must provide at least one of the following values in your request to this endpoint:

 *   `given_name`
 *   `family_name`
 *   `company_name`
 *   `email_address`
 *   `phone_number`

Winnings

Rollback

Retry Policy

Leverage all these API to build your own in-app payroll solution, customized for your users' needs

&lt;img src="https://516180.smushcdn.com/2880970/wp-content/uploads/2021/08/api-management-2200-2048x854.png?lossy=1&amp;strip=1&amp;webp=1" alt="">

#### How Are APIs Used By HR Software Providers?

Back in the bad old days before software that's hosted in the Cloud became the norm, APIs were designed to make it possible to connect different legacy software systems, which were often hosted on-premise (within the business location itself). Today, the ways in which APIs are applied is growing exponentially. Organisations with complex digital infrastructures use them to simplify data transfer. HR and ERP software providers use them to integrate seamlessly with other systems like Payroll and Time & Attendance. APIs facilitate data transfers that reduce the manual handling, time, and cost involved in importing and exporting (sharing) data.  

In combination with automated data validation (to check the accuracy and completeness of data that is uploaded to the system), the integrations between HR, Payroll and T&A solutions reduce processing times, decrease error rates, and eliminate the need for data double entry. Essentially, integrations are all about efficiency. They save you time, money, and energy.

#### APIs as HR and Payroll Software Enhancers

Most HR software Platforms provide APIs that you can use to integrate, automate, and orchestrate data sharing without writing code. In the HR and Payroll spaces, APIs make it easier to integrate and connect systems, services and data, create new user experiences, share information, and authenticate users. They enable transactions and algorithms and let you offer new services.

Using APIs, you can turn your HR software Platform into the source of truth in a digital ecosystem. With the right integrations, your HR Platform forms the hub in a spoke and wheel type configuration for real-time data sharing and improved decision-making across your entire organisation. Another benefit of using an HR [HR software Platform](https://www.subscribe-hr.com.au/blog/hr-software-from-product-to-platform) (as opposed to stand-alone HR solutions) with a high number of out-of-the-box integrations and an open API is that you will also be less dependent on any one vendor for managing the processes and tasks your business needs to digitise, automate and optimise. If you don’t like that particular product or service at some point in the future, or a better one becomes available, you can simply switch out one solution in your ecosystem for another via the API.

When you access pre-existing integrations through the vendor API instead of having new ones built (which might require the time and cost of a Developer), you save your business time and money. Here's an [estimate](https://blog.dreamfactory.com/api-calculator-understanding-the-costs-behind-building-an-api-based-application/) of what it costs to build a custom API from scratch:

> “An enterprise API costs an estimated $25,000-$30,000 to build, and then 50% of that amount per year to manage. Multiply that by 10 APIs and you have $275,000-$450,000 per year just so APIs can exist within your organisation. Everyone who wants to access an API must develop, test and implement custom code, at an estimated cost of $15,000 per integration, plus a 50% maintenance fee. Each API must also be secured, costing additional thousands of dollars.” 

No matter how sophisticated your HR solution (or suite of solutions) is, it will never cover all of the services you need or want to offer to your employees. Sometimes it will be necessary to exchange data with another service. Payroll is an excellent example. Or, you might want to make a completely new service available and that vendor only offers it through an API. APIs also happen to make life easier for your employees - if your HR software provider offers single sign-on, that means you can combine access to all the different software products you use via a single logon - meaning you give your people one place to go and help themselves to al the different business systems they need.

Service API

Open Game Url

List Game

Round Visual Details

Round Details

Round SmDetails

Update Balance

Promotions

GameDetails PT Legislation

Bet Details

Game Details

All of the stated endpoints and sections are for demonstration purposes only. Theneo does not manage payments API.  
Get sales data, itemize payments, push orders to POS, and more.

**⚠️ Note:** The Orders API provides a one-stop shop for integrating advanced payment functionality. You can itemize payments with custom line items or catalog objects, send orders to real Point of Sale devices to be fulfilled, and more.

In addition, the Orders API allows you to look through all of a seller's previous sales and returns itemization data, customer references, and other information from POS or online transactions.

&lt;img src="https://media.geeksforgeeks.org/wp-content/cdn-uploads/20200318193845/Top-7-Payment-Gateway-APIs-That-Every-Developer-Must-Know.png">

As an organization, you need to be careful while choosing a payment gateway option. It should be according to the customer’s experience on your websites through to cash flow to online sales. Make sure that you take care of at least 5 things mentioned below while choosing a payment gateway… 

- **Security** should be the topmost priority. Make sure that it should be integrated with the 3D security and comply with the PCI Data Security Standard (PCI DSS).
- **Payout Time** should be less to credit money in your bank account.
- **Integration need to be easy and simple** or it can develop a custom-coded solution for your platform easily.
- **Multiple currencies** should be handled by the payment gateway for the customers using different currencies across the world.

Appendix

Data Types

Response Codes

Locking/Unlocking Users Policy

Theneo Demo TechCrunch

Darwin Gaming System API

Production

<h2 class="slate-h2 " >🚀 <strong class="slate-bold">Introduction</strong></h2><p class="slate-p slate-indent-0" style="0px">This document provides a walk-through of Darwin’s Gaming System API (DGSAPI), which offers a simple solution to integrate with the Darwin Gaming System. It is organized around <a href="http://en.wikipedia.org/wiki/Representational_State_Transfer" target="_blank">REST</a>, with predictable resource-oriented URLs, accepts form-encoded request bodies, returns <a href="http://www.json.org/" target="_blank">JSON-encoded</a> responses, and uses standard HTTP response codes, authentication, and verbs.</p><p class="slate-p slate-indent-0" style="0px">A brief and simple overview of Darwin’s Gaming System (DGS) will also be provided, covering its components, the technologies used, and where it is deployed.</p><p class="slate-p slate-indent-0" style="0px">Darwin uses Google Cloud Platform (GCP) to host its containerized application. All aspects of DGS are carefully orchestrated through Google Kubernetes Engine (GKE). DGS design ensures portability across clouds and on-premises as it can run anywhere Kubernetes is supported.</p><p class="slate-p slate-indent-0" style="0px">Each client has a dedicated deployment of DGS within Darwin’s cluster with at least two environments, production and testing.</p><h2 class="slate-h2 " ><strong class="slate-bold">
Darwin Gaming System Overview</strong></h2><p class="slate-p slate-indent-0" style="0px">Darwin Gaming System (DGS) is a B2B game provider service that integrates seamlessly with operators. Through a simple integration with the operator’s wallet platform, all Darwin games become available and any additional future content becomes instantly accessible as it is added</p><p class="slate-p slate-indent-0" style="0px">DGS is a composition of Docker containerized applications and Google Cloud Services:</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Game Manager:</strong> Backend application developed in Python using the Django framework. It manages game logic and configurations, wallet integration, and reporting.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">DB Relational database:</strong> where all transactions are stored. In development and on-premises deployment, it uses MySQL. When running in GCP it uses Google Cloud SQL.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Cache: </strong>In-memory cache to store temporary data using REDIS.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Web Server:</strong> Web server and reverse proxy using NGINX</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">RNG</strong>: RNG and game internal logic developed in Python using the Falcon framework.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Wallet Internal:</strong> The wallet used in development environments is also used for free-to-play deployments (demo mode). Developed in Python using the Django framework.</div></li></ul><h2 class="slate-h2 " ><strong class="slate-bold">
Infrastructure Overview</strong></h2><h3 class="slate-h3 " ><strong class="slate-bold">Cloudflare</strong></h3><p class="slate-p slate-indent-0" style="0px">Darwin&apos;s system uses Cloudflare to optimize and protect its applications. All traffic to DGS goes through Cloudflare’s service. (More on the advantages of using Cloudflare <a href="https://www.cloudflare.com/" target="_blank">here</a>.)</p><p class="slate-p slate-indent-0" style="0px">For security reasons, the access to stage and testing environments is IP-restricted by Cloudflare’s Web Application firewall and needs to be whitelisted.</p><h3 class="slate-h3 " ><strong class="slate-bold">Google Cloud Plataform</strong></h3><p class="slate-p slate-indent-0" style="0px">GCP provides a reliable and highly scalable infrastructure to build, test, and deploy applications. DGS takes advantage of all the power of GCP delivering a stable and secure system with on-demand scalability and high availability.</p><h3 class="slate-h3 " ><strong class="slate-bold">Namespaces</strong></h3><p class="slate-p slate-indent-0" style="0px">Each operator integrated with Darwin’s System is attributed to a namespace within Darwin’s cluster. This organization provides independence for each operator, ensuring the best security and performance for all.</p><h3 class="slate-h3 " ><strong class="slate-bold">Autoscaling</strong></h3><p class="slate-p slate-indent-0" style="0px">Autoscaling allows DGS to handle increased demand and automatically adjust capacity to maintain steady and appropriate performance.</p><h3 class="slate-h3 " ><strong class="slate-bold">Regional Clusters</strong></h3><p class="slate-p slate-indent-0" style="0px">GCP zones are very stable however, if improved availability is needed, DGS can be deployed using regional clusters and distribute the Kubernetes resources across multiple zones within a region. This will allow DGS to continue functioning even during an outage or downtime in an individual zone.</p><h2 class="slate-h2 " ></h2><p class="slate-p " ></p><p class="slate-p " ></p>

This document provides a walk-through of Darwin’s Gaming System API (DGSAPI), which offers a simple solution to integrate with the Darwin Gaming System. It is organized around 

, with predictable resource-oriented URLs, accepts form-encoded request bodies, returns 

 responses, and uses standard HTTP response codes, authentication, and verbs.

A brief and simple overview of Darwin’s Gaming System (DGS) will also be provided, covering its components, the technologies used, and where it is deployed.

Darwin uses Google Cloud Platform (GCP) to host its containerized application. All aspects of DGS are carefully orchestrated through Google Kubernetes Engine (GKE). DGS design ensures portability across clouds and on-premises as it can run anywhere Kubernetes is supported.

Each client has a dedicated deployment of DGS within Darwin’s cluster with at least two environments, production and testing.

Darwin Gaming System (DGS) is a B2B game provider service that integrates seamlessly with operators. Through a simple integration with the operator’s wallet platform, all Darwin games become available and any additional future content becomes instantly accessible as it is added

DGS is a composition of Docker containerized applications and Google Cloud Services:

Darwin's system uses Cloudflare to optimize and protect its applications. All traffic to DGS goes through Cloudflare’s service. (More on the advantages of using Cloudflare 

For security reasons, the access to stage and testing environments is IP-restricted by Cloudflare’s Web Application firewall and needs to be whitelisted.

GCP provides a reliable and highly scalable infrastructure to build, test, and deploy applications. DGS takes advantage of all the power of GCP delivering a stable and secure system with on-demand scalability and high availability.

Each operator integrated with Darwin’s System is attributed to a namespace within Darwin’s cluster. This organization provides independence for each operator, ensuring the best security and performance for all.

Autoscaling allows DGS to handle increased demand and automatically adjust capacity to maintain steady and appropriate performance.

GCP zones are very stable however, if improved availability is needed, DGS can be deployed using regional clusters and distribute the Kubernetes resources across multiple zones within a region. This will allow DGS to continue functioning even during an outage or downtime in an individual zone.

<p class="slate-p slate-indent-0" style="0px">
Darwin is very flexible regarding the needs of our clients and will gladly implement an operator’s API if it eases the integration. In case the operator prefers we supply the following API.</p><p class="slate-p slate-indent-0" style="0px">DGSAPI is composed of six operations, each one represented by an endpoint, all requests will be made from DGS to the operator’s wallet platform.</p><div class="published-table"><div class="table-container" style="padding-left: 0px;"><table class="slate-table" style="min-width:100%;"><div class="published-table-header" style="width:100%;min-width:100%;min-height:initial;visibility: hidden;border:initial"><div style="width:100px;">Title</div><div style="width:100px;">Description</div><div style="width:100px;">Title</div></div><colgroup ><col style="width:initial"><col style="width:initial"><col style="width:initial"></colgroup><tbody class="slate-TableElement-tbody"><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">Operation</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">HTTP Method</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">Details</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">get account details</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">GET</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">Returns player details such as a unique ID, currency and language</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">get balance</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">GET</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">Returns the current balance in the specific player account</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">bet</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">POST</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">Informs the wallet that the player placed a bet</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">winnings</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">POST</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">Awards one or more winnings of a bet, and closes the game  round</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">rollback</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">POST</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">Cancels a specific bet and refunds that bet amount to the player</p></td></div></tr></tbody></table></div></div><p class="slate-p slate-indent-0" style="0px">DGSAPI uses session-based authentication and the operator must ensure that each player has a unique ID.</p><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">Note:</strong> Darwin is always open to our customer’s requests, if you need any change or have any special request on the API and its workings, please let us know.</p><p class="slate-p slate-indent-0" style="0px">The following sequence diagram is an example of a normal game interaction between DGS and the operator’s Wallet. It’s important to notice that all common parameters are always present in each type of operation request.</p><p class="slate-p " ></p><div style="text-align:center"><figure ><div style="display:inline-block"><img src="https://theneo-prod-public.s3.amazonaws.com/images-1700154224037.jpg" alt="" style="
              width:2302px;
	            height:2095px;
	            aspect-ratio:2302 / 2095"
         /></div></figure></div><h2 class="slate-h2 " ><strong class="slate-bold">
General Notes</strong></h2><p class="slate-p slate-indent-0" style="0px">All operators shall take into account the following when integrating with DGS</p><h3 class="slate-h3 " ><strong class="slate-bold">Assertion</strong></h3><p class="slate-p slate-indent-0" style="0px">DGS asserts that all parameters sent match the returned values.</p><h3 class="slate-h3 " ><strong class="slate-bold">Idempotence</strong></h3><p class="slate-p slate-indent-0" style="0px">Operators wallet platform shall have idempotence; i.e. receiving more than one bet request (if identical) shall register only once in the wallet platform. If there is a need to retry an operation (in case of a network error or response code with an error) the platform must ensure that the operation is carried out only once, allowing DGS to safely retry the operations.</p><h3 class="slate-h3 " ><strong class="slate-bold">Timeouts</strong></h3><p class="slate-p slate-indent-0" style="0px">All requests shall have a timeout of 15 seconds to prevent resource exhaustion.</p><h3 class="slate-h3 " ><strong class="slate-bold">Open Rounds</strong></h3><p class="slate-p slate-indent-0" style="0px">A round is considered open from the moment that the first successful bet has been placed and remains open until a successful call has been made with the parameter gamestatus has finished.</p><p class="slate-p slate-indent-0" style="0px">A round can have multiple transactions of the type of bet and winnings.</p><p class="slate-p " ></p><div class="slate-hr"><hr contenteditable="false" class="slate-HrElement-hr"/></div><p class="slate-p " ></p><h2 class="slate-h2 " ><strong class="slate-bold">Request Format</strong></h2><p class="slate-p slate-indent-0" style="0px">All DGSAPI requests:</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">use user and password authentication</div></li><li class="slate-li " ><div style="position:relative">are URL encoded</div></li><li class="slate-li " ><div style="position:relative">data is assumed to be encoded in UTF-8</div></li></ul><p class="slate-p slate-indent-0" style="0px">The following list of parameters is considered mandatory and is always provided in requests to the operator’s wallet platform, regardless of which endpoint being called.</p><p class="slate-p slate-indent-0" style="0px">List of mandatory parameters:</p><div class="published-table"><div class="table-container" style="padding-left: 0px;"><table class="slate-table" style="min-width:100%;"><div class="published-table-header" style="width:100%;min-width:100%;min-height:initial;visibility: hidden;border:initial"><div style="width:100px;">Title</div><div style="width:100px;">Description</div><div style="width:100px;">Title</div><div style="width:100px;">Description</div></div><colgroup ><col style="width:initial"><col style="width:initial"><col style="width:initial"><col style="width:initial"></colgroup><tbody class="slate-TableElement-tbody"><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">Parameter</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">Description</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">Type</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">Example Value</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">requestType</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">Request entry point name</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">Char</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">winnings</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">currency</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">The selected currency. (ISO 4217)</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">List</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">[&quot;EUR&quot;]</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">user</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">Username representing the login on the operator wallet</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">Char</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">user-123</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">password</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">Password for login on operator wallet</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">Char</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">qoF4SaI56f915&amp;Q</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">gameID</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">Unique Game ID configured in DGS instance</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">List</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">[&quot;Blackjack&quot;]</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">token</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">Operator generated session ID token passed on to the game provider at game launch</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">List</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">[&quot;edhabgt4bshbfkokpal&quot;]</p></td></div></tr></tbody></table></div></div><p class="slate-p slate-indent-0" style="0px">It is important to notice that the sessionID parameter should expire after some time of inactivity from the player, for security reasons. Even after expiration, some operations must be accepted to guarantee the data integrity between the <strong class="slate-bold">wallet</strong> and <strong class="slate-bold">DGS</strong> - more on this in the following chapters.</p><h2 class="slate-h2 " ><strong class="slate-bold">
Response Format</strong></h2><p class="slate-p slate-indent-0" style="0px">Darwin uses UTF-8 encoded JSON as the preferred format for all responses. Example as follows:</p><div class="code-block-wrapper"  style="width:100%;min-width:100%" ><div class="code-block-header">Plain text</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden"> </textarea><code class="language-json keep-markup drop-tokens"><div class="slate-code_line">{</div><div class="slate-code_line">  &quot;requestType&quot;: &quot;REQUEST_TYPE&quot;,</div><div class="slate-code_line">  &quot;rc&quot;: &quot;RESPONSE_CODE&quot;,</div><div class="slate-code_line">  &quot;accountID&quot;: &quot;ACCOUNT_ID&quot;,</div><div class="slate-code_line">  &quot;gameID&quot;: &quot;GAME_ID&quot;,</div><div class="slate-code_line">  &quot;balance&quot;: &quot;BALANCE&quot;,</div><div class="slate-code_line">  &quot;currency&quot;: &quot;CURRENCY&quot;</div><div class="slate-code_line">}
</div></code></pre></div><p class="slate-p slate-indent-0" style="0px">All responses have the following parameters:</p><div class="published-table"><div class="table-container" style="padding-left: 0px;"><table class="slate-table" style="min-width:100%;"><div class="published-table-header" style="width:100%;min-width:100%;min-height:initial;visibility: hidden;border:initial"><div style="width:100px;">Title</div><div style="width:100px;">Description</div><div style="width:100px;">Title</div><div style="width:100px;">Description</div></div><colgroup ><col style="width:initial"><col style="width:initial"><col style="width:initial"><col style="width:initial"></colgroup><tbody class="slate-TableElement-tbody"><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">Parameter</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">Description</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">Type</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">Example Value</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">request</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">Request entry point name</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">Char</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">winnings</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">rc</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">Response Code</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">Char</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">0</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">gameID</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">Unique Game ID configured in DGS instance</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">Char</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">Blackjack</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">accountID</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">The player’s unique ID</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">Char</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">2501112</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">currency</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">The selected currency. (ISO 4217)</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">Char</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">EUR</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">balance</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">The player’s current balance (in cents)</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">Int</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px">12354</p></td></div></tr></tbody></table></div></div><p class="slate-p " ></p><p class="slate-p " ></p>


Darwin is very flexible regarding the needs of our clients and will gladly implement an operator’s API if it eases the integration. In case the operator prefers we supply the following API.

DGSAPI is composed of six operations, each one represented by an endpoint, all requests will be made from DGS to the operator’s wallet platform.

Title

Description

DGSAPI uses session-based authentication and the operator must ensure that each player has a unique ID.

 Darwin is always open to our customer’s requests, if you need any change or have any special request on the API and its workings, please let us know.

The following sequence diagram is an example of a normal game interaction between DGS and the operator’s Wallet. It’s important to notice that all common parameters are always present in each type of operation request.

All operators shall take into account the following when integrating with DGS

DGS asserts that all parameters sent match the returned values.

Operators wallet platform shall have idempotence; i.e. receiving more than one bet request (if identical) shall register only once in the wallet platform. If there is a need to retry an operation (in case of a network error or response code with an error) the platform must ensure that the operation is carried out only once, allowing DGS to safely retry the operations.

All requests shall have a timeout of 15 seconds to prevent resource exhaustion.

A round is considered open from the moment that the first successful bet has been placed and remains open until a successful call has been made with the parameter gamestatus has finished.

A round can have multiple transactions of the type of bet and winnings.

The following list of parameters is considered mandatory and is always provided in requests to the operator’s wallet platform, regardless of which endpoint being called.

It is important to notice that the sessionID parameter should expire after some time of inactivity from the player, for security reasons. Even after expiration, some operations must be accepted to guarantee the data integrity between the 

 - more on this in the following chapters.

Darwin uses UTF-8 encoded JSON as the preferred format for all responses. Example as follows:

All responses have the following parameters:

<p class="slate-p slate-indent-0" style="0px">Darwin API also possesses a separate module named SAPI where is possible to retrieve details related to any round available and info from the operator.</p><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p>

Darwin API also possesses a separate module named SAPI where is possible to retrieve details related to any round available and info from the operator.

<p class="slate-p slate-indent-0" style="0px">In order to operate in the Portuguese gambling market, it’s mandatory by law that at the end of each round, the operator shares the player action history and the result of that same round with the Portuguese gambling market regulator <a href="https://api.darwininteractive.com/www.srij.turismodeportugal.pt" target="_blank">SRIJ</a>. Darwin already conducted a deep market study regarding this situation. Based on the results of that study, and our own personal experience operating in the Portuguese market, we suggest the following game details reporting structure:</p><p class="slate-p " >
</p><p class="slate-p " ></p><p class="slate-p " ></p>

In order to operate in the Portuguese gambling market, it’s mandatory by law that at the end of each round, the operator shares the player action history and the result of that same round with the Portuguese gambling market regulator 

. Darwin already conducted a deep market study regarding this situation. Based on the results of that study, and our own personal experience operating in the Portuguese market, we suggest the following game details reporting structure:

Sections