General API provision

Authorization

Our system uses key-based authentication. The authorization key is used for almost all requests and is the same for both the Game Flow API and the 100HP Gaming API.

ℹ️ Info

100HP Gaming provides a secret key for partners in preparation for integration.

Example of authorizted request to 100HP Gaming API

On our side, we will check the correctness of the secret you sent.

Example of request from Game Flow API authorization

def validate_secret(received_secret):
    expected_secret = "your_expected_secret_123"
    return received_secret == expected_secret
# Usage:
# request_is_authorizted = validate_secret(request_body_data["secret"])

You must check on your side that the secret sent is correct.

Resposne format

All responses use JSON format. Make sure your Game Flow API responses set the Content-Type:application/json header. We do the same on our side in the 100HP Gaming API to ensure proper data processing.

Decimal Precision

If parameters amount and balances has more than 2 decimal places, the decimal part should be truncated to 2 decimal places. For example, the amount = 104.129 should be truncated to 104.12.

Transaction ID Consistency

The txId parameter must be the same for withdrawal-deposit transactions to ensure proper tracking and error handling.

Handling duplicate transactions after rollback

In the event that a deposit with the same transaction ID as a successful rollback is received, an error response should be returned with the following details:

errCode: 608

message: "Transaction already refunded"

This error indicates that the transaction has already been refunded, and no further action is necessary.

Handling duplicate rollbacks after deposit

In the event that a rollback with the same transaction ID as a successful deposit is received, an error response should be returned with the following details:

errCode: 609

message: "Transaction already settled"

This error indicates that the transaction has already been settled, and no further action is necessary.

Errors format

ℹ️ Info

The HTTP error code must match the errCode

Error parameters

Parameters	Type	Required	Description
`data`	`string`	✅	Additional info. Can be empty
`message`	`string`	✅	Error message
`errCode`	`int`	✅	HTTP error code

Error schema

{
    "data": "string",
    "message": "string",
    "errCode": int
}

Authorization#

Example of authorizted request to 100HP Gaming API#

Example of request from Game Flow API authorization#

Resposne format#

Decimal Precision#

Transaction ID Consistency#

Handling duplicate transactions after rollback#

Handling duplicate rollbacks after deposit#

Errors format#

Error parameters#

Error schema#