Buffalo Game Seamless Integration – API Documentation

Our seamless integration differs slightly from normal seamless. Follow these rules for correct behavior.

Key Integration Rules

Game Launch: First, request a game URL from our API, then open it for the player.
Server → Server Logs: We send a log every spin/round. You must reply { "status": "ok" } immediately, or the round is terminated.
Balance Lock: Lock the player’s balance while playing. On round end we send exitInfos so you can unlock those users.

Game Environment

Purpose	Method	Endpoint
Game Launch URL	POST (JSON)	`https://api4.qianxu168.com/game/url`
Game Report Detail by TransactionID	POST (JSON)	`https://api4.qianxu168.com/inspect.php`

Game Launch

Request a launchable game URL, then open it in your player’s browser/iframe.

Request Body

Field	Type	Required	Description	Example
id	string	Yes	Your player’s username/ID	`"bf10799901"`
game	string	Yes	Game key/name	`"AfricanBuffalo"`
domain	string	Yes	Your tenant/brand identifier	`"buffalo688"`
balance	number	Yes	Starting balance snapshot (integer)	`5007`

{
  "id": "bf10799901",
  "game": "AfricanBuffalo",
  "domain": "buffalo688",
  "balance": 5007
}

Response Body

Field	Type	Description	Example
status	string	"ok" on success	`"ok"`
players	array	List of players with their balances	`[{"playerId":"bf123455","balance":1000.35}]`

{
  "status": "ok",
  "players": [
    {
      "playerId": "bf123455",
      "balance": 1000.35
    }
  ]
}

Open the game URL for the player after a successful response. The players array can include multiple players if needed.

Game Report Detail (by TransactionID)

Fetch round details for a specific transactionId (useful for BO/CS).

Request Body

Field	Type	Required	Description	Example
domain	string	Yes	Your tenant/brand	`"buffalo688"`
transactionId	string \| number	Yes	Transaction/Round identifier	`"1757263203983752334"`

{
  "domain": "buffalo688",
  "transactionId": "1757263203983752334"
}

Response shape depends on provider detail format. Use it for round diagnostics/verification.

Round-End Webhook (Sent to Your Server)

On each round end we POST a log to your webhook. You must ACK with { "status": "ok" }.

Payload Schema

Field	Type	Required	Description
detail	object	No	Reserved for extra metadata
domain	string	Yes	Your tenant/brand
exitInfos	array<object>	Yes	Players to unlock after the round (each item: `{ id: string }`)
game	string	Yes	Game name/code
matchNo	number	Yes	Provider match number
reportId	number	Yes	Unique report identifier
transactions	array<object>	Yes	Balance deltas and round entries (see below)

transactions[] Item

Field	Type	Required	Description	Example
amount	number	Yes	Delta to apply to user balance (can be + or -)	`-80`
balance	number	No	Provider-side running balance	`2075`
bet	number	No	Bet amount for this action	`80`
commission	number	No	Commission, if any	`0`
id	string	Yes	Player identifier (usually username)	`"buffalo1183768"`
playerType	string	No	Reserved	`""`
status	string	Yes	`win` \| `lose` \| `refund` \| `cancel`	`"lose"`
transactionId	string \| number	Yes	Unique transaction / round ID — store it	`1760357702072700000`

Sample Payload

{
  "detail": {},
  "domain": "buffalo688",
  "exitInfos": [
    {"id": "buffalo1183"},
    {"id": "buffalo11822"}
  ],
  "game": "AfricanBuffalo",
  "matchNo": 34424110,
  "reportId": 1760357702072694000,
  "transactions": [
    {
      "amount": -80,
      "balance": 2075,
      "bet": 80,
      "commission": 0,
      "id": "buffalo1183768",
      "playerType": "",
      "status": "lose",
      "transactionId": 1760357702072700000
    }
  ]
}

Processing Rules (Your Side)

For each transactions[] item: new_balance = old_balance + amount.
Persist transactionId as your round ID for BO checks.
Unlock all users listed in exitInfos.

ACK with:


{
  "status": "ok",
  "players": [
    {
      "playerId": "bf123455",
      "balance": 1000.35
    }
  ]
}

If you don’t ACK, we terminate the round.

Balance Locking Behavior

Set a strict lock when the user launches a Buffalo game (block withdrawals/transfers/other updates).
Only apply changes from our webhook logs during play.
Release the lock for all users listed in exitInfos at round end.

RTP Configuration

You can configure Return to Player (RTP) per agent. Without per-agent RTP, a global RTP applies.