02 / Login + Wallet Transfer APIs
Once you have your api_key and api_secret, you can begin integration.
API domain: https://gateway-api.bwsh7twk.com/
After the Login API integration is complete, use the redirect_url to redirect the player directly to the game page. Integrating the Wallet API afterward completes the integration.
There are four APIs in total:
2.1 Common Conventions
Response fields are always named in snake_case (for example, temporary_key, redirect_url, currency_code).
All responses are wrapped in a unified envelope:
json
{
"code": 0,
"message": "success",
"data": { /* Actual business payload; see each API for its structure */ }
}code == 0indicates success; the business data is in thedatafield.code != 0indicates failure; refer tomessage.
Common error code examples:
| code | message | Description |
|---|---|---|
| 10000 | authentication failed / missing body-hash in metadata | Signature or header is incorrect |
| 10020 | ticket_id is required | Missing required field |
| 10080 | internal server error | Internal server error |
For the complete error reference, see Common Integration Errors.
Next, read the HMAC Signing Flow. All APIs (including GET) require a correct signature to be called successfully.