Transactions API
Transaction API Reference - Operator API
Transactions API is an API which provides a list of all user's gameplay transactions, including their status and unique transaction IDs, which are crucial for processing transactions as well as troubleshooting any issues during gameplays.
Provides two response modes based on sessionId parameter:
With sessionId: Returns flat list of individual transactions for the session
Without sessionId: Returns transactions grouped by gaming sessions
Features:
Time range filtering required (startTime and endTime)
Supports multiple transaction types: BET, WIN, DEPOSIT, WITHDRAWAL
Pagination support (max 120 items per page)
Integrates with BgWallet service
Required headers: X-Player-Token
Sample request (with sessionId):
{
"startTime": "2025-10-01T00:00:00Z",
"endTime": "2025-10-08T23:59:59Z",
"sessionId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"page": 1,
"pageSize": 20
}Sample request for grouped sessions (without sessionId):
Sample response for individual transactions:
Sample response for grouped sessions:
Transaction Types:
BET: Debit transactions for game rounds
WIN: Credit transactions for game winnings
DEPOSIT: Wallet funding transactions
WITHDRAWAL: Wallet withdrawal transactions
REQUIRED - JWT Authorization header using the Bearer scheme. All API endpoints require authentication, except for authentication endpoints (Connect/authentication). Example: "Authorization: Bearer {token}"
Player access token for session validation
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...Successfully retrieved transaction data. Format depends on sessionId parameter presence.
Invalid request parameters, missing time range, invalid date format, or pagination errors.
Invalid or missing X-Player-Token header authentication.
No content
Last updated