General API Rules

This documentation is intended for the implementer of the InApi (“the game vendor / provider”). 

InApi endpoint acts as:

1. Game launcher - see chapter “Game Launch”.
2. A proxy for wallet service (InApi supports multiple wallet services). This allows for simpler and unified integration between game vendors and wallet service operators.

InApi is based on Betconstruct API and it adds new calls, scenarios and error codes on top of it.

HTTPS POST method is used for all requests. 

The Content-Type of request is application/json. 

The following parameters are general for all requests:

• time — request time, datetime string, with "DD-MM-YYYY HH:MM:SS" format
• data — json-encoded data, requested API method parameters
• hash — MD5 checks the sum of concatenated string, which consists of PrivateKey (given to partner) time and data.

• Hash — passkey + time + data

• Example: 12345678y!04-02-2021 14:57:35{“param”:”value”,”param”:”value”...}

Rules for optional parameters (e.g. roundId in Rollback):

• Send only when there’s value. Omit the parameter and its value completely from sent JSON if the value would be null.
• If you are sending the parameter, make it part of the hash calculation.

Definition of parties involved

• Game Provider - “GP” — the one who is calling InApi methods. Also called ”Game Vendor”.
• InApi - “IA”— the endpoint (or “server”) that receives requests from GP and forwards them to specific Wallet Service. Responses from WS (or errors involved) are forwarded back to GP.
• Wallet Service “WS”  — endpoint where specific implementation of wallet service resides.