Skip to main content

77G /Brand Merchantwallet documentation

77Gaming Brand Merchant Single Wallet API

OpenAPI specification for brand merchants integrating with the 77Gaming single-wallet platform.

Version
1.0.0
Format
OpenAPI 3.0.3
Endpoints
4

Integration reference

Integration Guide

​

Introduction / Important Notes

  • API endpoints

    Production: https://ex.77gapi.work
    Test: https://ex.588web.live
  • API parameters Share Key, Brand ID, Brand Domain Code, back-office URL, and login account are provided by our team upon request.

  • Before integrating, provide your connection IP addresses for whitelist access. Test environment IP access takes 2–3 days.

  • All APIs use GMT+8 (Beijing time).

  • API responses use JSON format.

  • All APIs require the ts (timestamp) parameter. Each request is validated to be within 20 seconds.

  • The full hierarchy can be configured in the back office.

  • Hierarchy: Partner > Operator > Brand Merchant > Member

    Partner: Partner tier. Operators can be created at this level.

    Operator: Operator tier under a partner. Brand merchants can be created at this level.

    Brand Merchant: Brand merchant tier under an operator. Members can be created at this level.

​

API Authentication Guide

Generate a hash to ensure the integrity and accuracy of API data transmission.

Hash rulemd5(parameter data (does not include the timestamp) + share key)
Share keytoken
  • Sort parameter keys alphabetically from a to z.
  • Arrays do not need to be encrypted.
  • Concatenate parameter data as key=value&key=value.
  • If an API call has issues, provide the full request parameters, headers, the pre-hash string, and the received response.

Request data

{ "user_id": 1, "username": "test" }

Generate hash

MD5(user_id=1&username=test&shared_key=token)

API parameters example

{ "hash": "e7770fc3ec1b6d5b2c49e92c73c8f430", "ts": 1542080457, "brand_id": 1, "is_thumbnail_required": true }

Brand Merchant Flow​

Notes​

OpenAPI reference

API Reference​