API Documentation

Use the Buffalo API to authenticate, launch, and more and seamlessly integrate your platform into the endless Buffalo world of online games. Upon authenticating, all the Buffalo games use the Seamless Wallet for integration.

Getting started

To get started, read about how to make requests for the resources you need to access using our HTTP APIs. When your integration is ready to go live please reach out the Buffalo Game support team.

For One Wallet integration, Buffalo.games system accesses the player’s wallet in the operator’s system in real time to retrieve player’s balance and to perform credit, debit and cancel transactions. Expected call processing time is less than 300 milliseconds. Longer processing of a request and delivery of a reply increases portion of cancelled bets and gives bad user experience. This communication is handled by the Buffalo.games One Wallet server. Please consult your Key Account Manager (KAM) for slots specific content availability for your integration.

One Wallet API protocol has the following features:

RESTful protocol with lightweight JSON-formatted requests and responses Requests and responses contain the header Content-Type: application/json Responses contain the header Connection: keep-alive to allow persistent connection Requests are made via HTTP POST method Communication happens over HTTPS to ensure security and privacy. Unencrypted HTTP is not supported All requests passed to the Licensee’s system have authentication token (API token) in the authToken query parameter:

API token is a string that ensures requests can be authenticated by the operator’s system. API token is typically generated by the Licensee and securely shared with Evolution. API token should contain only URL-safe symbols, as defined in Section 2.3 of RFC 3986: A-Z, a-z, 0-9, -, ., _ and ~. API token’s length is recommended to be between 8 and 22 symbols. Certain symbols in the Host Name and some Top-level Domains are not allowed to be integrated with One Wallet:

List of TLDs not allowed by One Wallet: .dev, .live. Rules and symbols for host names allowed by One Wallet are defined in Section 2.3.1 of RFC 5890: A-Z, a-z, 0-9, -, ..

UTC timezone

Throughout this document and in the API responses, we are using the UTC timezone.

SID overview

sid is an attribute used in One Wallet API calls and represents player’s session ID. Buffalo.games gets sid value from operator in Game Launch call as player.sid.

In settlement calls (CreditRequest/CancelRequest) Buffalo.games will use the same sid that was used in corresponding DebitRequest.

SID validation

Operator should validate if sid received in Buffalo.games calls has ever been issued.

sid should not expire even if the player’s session has already been terminated. I.e. even if the session does not exist anymore Operator should accept:

settlement calls (CreditRequest/CancelRequest) for those DebitRequests that were successfully accepted previously This might be needed in such cases as:

the player logged out but the game continues and settlement needs to be done even if the player went offline environmental issues (e.g service is down, network is down)