Seamless Mode
This page outlines the workflow for Seamless Integration.
Last updated
This page outlines the workflow for Seamless Integration.
Last updated
The SlotCity API offers seamless integration, providing the flexibility to manage your users' balances directly. With Seamless Mode, you can handle deposits, withdrawals, log history, and generate statistics independently.
This approach isolates your users' balances, ensuring you are protected from any potential malicious activities by API providers.
By using this mode, you can seamlessly integrate multiple APIs within your casino. This allows you to manage various functionalities, such as user balances and transactions, across different API providers without any conflicts. It ensures smooth operation and flexibility, enabling you to leverage the strengths of different APIs simultaneously.
In this mode, our API will send specific requests to retrieve necessary information, such as the user's balance and authority. It will also update the user's balance whenever they place a bet and win or lose, by communicating with your casino's backend and processing the results.
Here is a diagram that explains the workflow in Seamless Mode.
Callback URL is an endpoint that our API can access over the internet and send callback requests.
To set a callback URL, navigate to the [Settings] page within our back office system. This is where you can configure various settings related to your account and operations.
The callback URL you enter must begin with either http:// or https://. This ensures that the URL is correctly formatted and can be accessed over the web. For example, a valid callback URL might look like this: https://test.com/callback.
After you set the callback URL, it may take up to 10 minutes for the changes to be applied to the real server. This delay allows the system to properly update and ensure that the new URL is correctly integrated.
If you are using the transfer wallet mode, you should leave the Callback URL field empty. This is because the transfer wallet mode does not require a callback URL for its operations.
You can learn how to implement callback processing code by referring to our Seamless Integration Code Examples.
After referring to the Seamless Integration Code Examples, you must implement all functions.
At this stage, you need to implement server-side code to handle our callback requests. Specifically, you should create an endpoint using the Callback URL that can listen for incoming callback requests from our system. This endpoint should be capable of parsing the callback request data and responding with the appropriate information or error message.
In summary:
Create an Endpoint: Develop an endpoint on your server that matches the Callback URL.
Listen for Requests: Ensure this endpoint is set up to listen for incoming callback requests from our system.
Parse the Request: Write code to parse the data contained in the callback request.
Respond Appropriately: Based on the parsed data, return the necessary information or an error message if something goes wrong.
By following these steps, you can effectively handle our callback requests and ensure smooth communication between our systems.
You are responsible for any non-implementation.
You can review our callback request specifications on the Callback Requests page. Additionally, you can learn how to respond to our callback requests on the Callback Responses page.
When writing the callback processing code, please refer to the [API Error Logs] page in our back office. You can view all errors on this page and debug your code based on these error logs.
Variable Type Caution! Please refer to the example codes and develop it according to string and int variable types.
In the case of string, it is marked with single quotation marks, such as 'test', and in the case of balance, it must be matched with int type, such as 1000.
Begin by navigating to the [API/Callback API Testing] page within our back office system. This page is specifically designed to guide you through the testing process in a structured manner. Follow each step as outlined on the page to ensure that all aspects of the callback API are thoroughly tested.
During the testing phase, you will be working with virtual data. This means that you do not need to use actual points from your wallet. The virtual data will simulate real transactions and scenarios, allowing you to test the functionality of the callback API without impacting your actual point balance.
If you find that you need actual test points for a more realistic testing scenario, you will need to obtain approval from your agent first. Once you have received this approval, you can then submit a request for the necessary test points. This ensures that all test points are allocated appropriately and with proper authorization.
Please operate after passing all tests. You are responsible for any non-implementation.
Lastly, please access API in the Main API to test the actual game.
