Tigoo

Introduction

Authentication

Endpoints

Health

Get games list

Create User

Create Game Link

Webhook

Balance

Loss

[TIGOO]

Production

Sandbox

The Introduction section provides an overview of the TIGOO API, which allows you to integrate TIGOO functionality into your applications. This API documentation is designed to be clear and structured, ensuring that both developers and non-technical roles can easily understand and utilize the API.The TIGOO API offers a wide range of functionality to enhance your applications. From retrieving data to creating and modifying widgets, this API enables seamless integration with TIGOO.The API endpoints provide different functionalities, such as retrieving widgets, managing user data, and handling various actions within the TIGOO system. Each endpoint has specific use-cases that can be leveraged to enhance your application&apos;s user experience.To facilitate straightforward API integration, this documentation includes comprehensive information about the various endpoints, their parameters, and the expected responses. The goal is to ensure that developers can efficiently implement TIGOO functionality and non-technical roles can understand the API&apos;s capabilities without requiring extensive technical knowledge.Please refer to the respective sections of this documentation for detailed information on each API endpoint, including examples and any special considerations. By following the provided guidelines, you will be able to seamlessly integrate TIGOO into your applications and leverage its powerful features to enhance your user experience.

The Introduction section provides an overview of the TIGOO API, which allows you to integrate TIGOO functionality into your applications. This API documentation is designed to be clear and structured, ensuring that both developers and non-technical roles can easily understand and utilize the API.

The TIGOO API offers a wide range of functionality to enhance your applications. From retrieving data to creating and modifying widgets, this API enables seamless integration with TIGOO.

The API endpoints provide different functionalities, such as retrieving widgets, managing user data, and handling various actions within the TIGOO system. Each endpoint has specific use-cases that can be leveraged to enhance your application's user experience.

To facilitate straightforward API integration, this documentation includes comprehensive information about the various endpoints, their parameters, and the expected responses. The goal is to ensure that developers can efficiently implement TIGOO functionality and non-technical roles can understand the API's capabilities without requiring extensive technical knowledge.

Please refer to the respective sections of this documentation for detailed information on each API endpoint, including examples and any special considerations. By following the provided guidelines, you will be able to seamlessly integrate TIGOO into your applications and leverage its powerful features to enhance your user experience.

The Endpoints section of the TIGOO API documentation provides access to various functionalities within the system. These endpoints allow you to interact with TIGOO programmatically and integrate it into your own applications seamlessly.With TIGOO, you have the ability to retrieve, create, update, and delete various resources. These resources include widgets, which are the building blocks of TIGOO&apos;s interface.By utilizing the provided endpoints, you can retrieve information about specific widgets or perform actions such as creating new widgets, updating existing ones, or removing them from your TIGOO instance.Notably, the endpoints offer flexibility and customization options to suit your specific use-case. Whether you are a developer looking to enhance the functionality of TIGOO or a non-technical user seeking to streamline your workflow, these API endpoints provide the necessary tools.Please refer to the relevant sections in this documentation for detailed information on each endpoint, including the required parameters, response examples, and any additional considerations specific to that endpoint.By leveraging TIGOO&apos;s API endpoints, you can seamlessly integrate TIGOO into your own systems, enabling a smooth and efficient workflow for your organization or project.

The Endpoints section of the TIGOO API documentation provides access to various functionalities within the system. These endpoints allow you to interact with TIGOO programmatically and integrate it into your own applications seamlessly.

With TIGOO, you have the ability to retrieve, create, update, and delete various resources. These resources include widgets, which are the building blocks of TIGOO's interface.

By utilizing the provided endpoints, you can retrieve information about specific widgets or perform actions such as creating new widgets, updating existing ones, or removing them from your TIGOO instance.

Notably, the endpoints offer flexibility and customization options to suit your specific use-case. Whether you are a developer looking to enhance the functionality of TIGOO or a non-technical user seeking to streamline your workflow, these API endpoints provide the necessary tools.

Please refer to the relevant sections in this documentation for detailed information on each endpoint, including the required parameters, response examples, and any additional considerations specific to that endpoint.

By leveraging TIGOO's API endpoints, you can seamlessly integrate TIGOO into your own systems, enabling a smooth and efficient workflow for your organization or project.

API Description:
The Health API endpoint allows you to check the status of the TIGOO project. By making a GET request to this endpoint, you will receive a response containing the current status of the project.This API is useful for monitoring the overall health of the TIGOO project and ensuring smooth integration with other systems. It can be used by both developers and non-technical roles to quickly assess the status and availability of the project.The response will include a status code indicating the overall health of the project. A status code of 200 signifies that the project is running smoothly, while a status code of 503 indicates that the project is temporarily unavailable.By regularly checking the health of the TIGOO project using this API, you can proactively detect any issues and take appropriate actions to ensure the smooth functioning of your integration.Please note that this API does not require any additional parameters to be included in the request. Simply make a GET request to the /health endpoint and receive the status response.Integrating the Health API into your workflow will provide you with crucial information about the availability and performance of the TIGOO project, enabling you to make informed decisions and troubleshoot any potential issues efficiently.

API Description:
The Health API endpoint allows you to check the status of the TIGOO project. By making a GET request to this endpoint, you will receive a response containing the current status of the project.

This API is useful for monitoring the overall health of the TIGOO project and ensuring smooth integration with other systems. It can be used by both developers and non-technical roles to quickly assess the status and availability of the project.

The response will include a status code indicating the overall health of the project. A status code of 200 signifies that the project is running smoothly, while a status code of 503 indicates that the project is temporarily unavailable.

By regularly checking the health of the TIGOO project using this API, you can proactively detect any issues and take appropriate actions to ensure the smooth functioning of your integration.

Please note that this API does not require any additional parameters to be included in the request. Simply make a GET request to the /health endpoint and receive the status response.

Integrating the Health API into your workflow will provide you with crucial information about the availability and performance of the TIGOO project, enabling you to make informed decisions and troubleshoot any potential issues efficiently.

The status parameter is used to retrieve the current health status of the system. It indicates whether the system is operating normally or if there are any issues or errors. The possible values for this parameter include "healthy" to indicate that the system is functioning properly, and "unhealthy" to indicate that there may be some issues or errors that need attention.

status

Get games list: Section allows users to retrieve a list of games. By making a request to this section, users can obtain information such as the unique ID, name, and logo image associated with each game.

Get games list: Section allows users to retrieve a list of games. By making a request to this section, users can obtain information such as the unique ID, name, and logo image associated with each game.

The Content-Type header parameter specifies the format of the request payload. It indicates the media type of the data being sent.

Content-Type

The Authorization header parameter is used to authenticate the request. It typically contains a token or credentials to verify the identity and permissions of the user making the request.

Authorization

Create User: This API endpoint allows you to create a new user in the [TIGOO] project. By sending a POST request to /users, you can provide the necessary information in the request body, including the user&apos;s identifier, currency, and country. Upon successful creation, the API will return a status code of 200 and provide details such as the user&apos;s status, a message, and their unique ID. This functionality enables easy user creation and integration within the project.

Create User: This API endpoint allows you to create a new user in the [TIGOO] project. By sending a POST request to /users, you can provide the necessary information in the request body, including the user's identifier, currency, and country. Upon successful creation, the API will return a status code of 200 and provide details such as the user's status, a message, and their unique ID. This functionality enables easy user creation and integration within the project.

The unique identifier for the user being created. This identifier is typically an email address or a username.

identifier

The currency in which the user operates. This parameter is used to specify the user's preferred currency for financial transactions.

currency

The country in which the user is located. This parameter is used to specify the user's geographical location.

country

The type of content being sent in the request body. This parameter specifies the format of the data being transmitted, such as JSON or XML.

The authentication token or credentials used to authorize the API request. This parameter ensures that only authorized users can create new users.

The status of the user creation request. This parameter indicates whether the user creation was successful or encountered an error.

A descriptive message providing additional information about the user creation status. This message can be used for troubleshooting or error handling purposes.

message

The unique identifier assigned to the newly created user. This identifier can be used to reference the user in subsequent API calls.

Create Game Link allows users to generate a unique URL that can be used to access a specific game. By making a POST request to the /game endpoint, users can create a game link by providing the required parameters: user_id and game_id. Upon successful creation, a response with a status code of 200 will be returned, including the status, message, and the generated URL. In case of any errors or missing parameters, a response with a status code of 400 will be returned, providing the status and error message. This API endpoint simplifies the process of generating game links and integrates seamlessly into various applications.

Create Game Link allows users to generate a unique URL that can be used to access a specific game. By making a POST request to the /game endpoint, users can create a game link by providing the required parameters: user_id and game_id. Upon successful creation, a response with a status code of 200 will be returned, including the status, message, and the generated URL. In case of any errors or missing parameters, a response with a status code of 400 will be returned, providing the status and error message. This API endpoint simplifies the process of generating game links and integrates seamlessly into various applications.

The user_id parameter is a unique identifier for a user. It is used to associate the user with the game and perform actions specific to their account.

user_id

The game_id parameter is a unique identifier for a game. It is used to associate the game with its corresponding data and actions.

game_id

The status parameter indicates the status of the game creation request. It provides information about whether the request was successful or encountered an error.

The message parameter contains additional information or error messages related to the game creation request. It provides more context about the status of the request.

The url parameter contains the URL of the created game link. It is returned in the response body after successfully creating a game link.

The Webhook section of the TIGOO API allows you to receive real-time notifications about events that occur within the system. A webhook is a way for us to send a POST request to a URL of your choice whenever a specific event, such as a new order or a user registration, occurs.By integrating with webhooks, you can automate workflows and update external systems in response to events happening in TIGOO. This can be especially useful for tasks like sending email notifications, syncing data with a CRM, or triggering custom actions in your own application.To set up a webhook, you need to provide us with the URL where you want the notifications to be sent. Our system will then make a POST request to that URL with the relevant data whenever an event occurs. You can specify which events you want to be notified about by configuring the webhook settings in your TIGOO account.It&apos;s important to note that the URL you provide should be publicly accessible over the internet. Additionally, you should ensure that your server can handle the incoming POST requests and process the data sent in the request body.Webhooks provide a reliable and efficient way to stay updated with the latest events happening in TIGOO. By leveraging webhooks, you can streamline your workflows and improve the overall integration between TIGOO and your own systems.

The Webhook section of the TIGOO API allows you to receive real-time notifications about events that occur within the system. A webhook is a way for us to send a POST request to a URL of your choice whenever a specific event, such as a new order or a user registration, occurs.

By integrating with webhooks, you can automate workflows and update external systems in response to events happening in TIGOO. This can be especially useful for tasks like sending email notifications, syncing data with a CRM, or triggering custom actions in your own application.

To set up a webhook, you need to provide us with the URL where you want the notifications to be sent. Our system will then make a POST request to that URL with the relevant data whenever an event occurs. You can specify which events you want to be notified about by configuring the webhook settings in your TIGOO account.

It's important to note that the URL you provide should be publicly accessible over the internet. Additionally, you should ensure that your server can handle the incoming POST requests and process the data sent in the request body.

Webhooks provide a reliable and efficient way to stay updated with the latest events happening in TIGOO. By leveraging webhooks, you can streamline your workflows and improve the overall integration between TIGOO and your own systems.

Sections