Wallet Transactions History

This endpoint allows you to retrieve the history of wallet transactions. It provides detailed information about each transaction, including the type, amount, and associated identifiers such as market, bet, and event IDs. This is useful for tracking financial activities within the wallet, such as bets placed, deposits made, and withdrawals processed.

Endpoint

GET /v2/mm/get_transactions

Description

Retrieve a comprehensive history of wallet transactions. This endpoint supports various filters to narrow down the results, such as transaction type, market ID, bet ID, and event ID. It also supports pagination through the next_cursor parameter, allowing you to fetch subsequent pages of results.

Parameters

next_cursor (query, string): Use this for pagination to fetch the next page of results.
to (query, integer): The end timestamp for the transaction history. Example: 1664617512.
from (query, integer): The start timestamp for the transaction history. Example: 1664790312.
limit (query, integer): The maximum number of transactions to return. The default is 20, and the maximum is 1000.
market_id (query, string): Filter transactions by market ID.
bet_id (query, string): Filter transactions by bet ID.
event_id (query, string): Filter transactions by event ID.
transaction_type (query, string): Filter transactions by type. Possible values include BET, DEPOSIT, REFUND, PAY, WITHDRAW, COMMISSION, ADJUSTMENT_REDUCE, ADJUSTMENT_INCREASE, VOID, REJECT_WITHDRAW, APPROVE_WITHDRAW, CANCEL, PUSH.

Responses

200 OK: Returns a list of transactions matching the specified criteria.
400 Bad Request: The request was invalid, often due to incorrect parameters.
401 Unauthorized: Authentication failed or was not provided.
500 Internal Server Error: An error occurred on the server.

Usage

This endpoint is ideal for users who need to audit their transaction history or integrate wallet transaction data into their financial systems. By using the available filters, users can efficiently locate specific transactions or analyze transaction patterns over time.