Play History Endpoint

This endpoint allows users to retrieve detailed play histories. It is designed for market makers who need to track and analyze their betting activities over a specified period. The endpoint supports various filters to refine the search results, making it easier to find specific plays based on different criteria.

Endpoint Details

URL: /mm/get_wager_histories
Method: GET
Security: Requires a valid token for authentication.

Parameters

to (integer, query): The end timestamp for the play history retrieval. Example: 1664617512.
from (integer, query): The start timestamp for the play history retrieval. Example: 1664790312.
page (integer, query): The page number for pagination. Default is 1.
limit (integer, query): The number of records per page. Default is 20.
market_id (string, query): Filter results by market ID.
matching_status (string, query): Filter results by matching status. Options include unmatched, fully_matched, and partially_matched.
status (string, query): Filter results by play status. Options include void, closed, canceled, manually_settled, inactive, wiped, open, invalid, and settled.
event_id (string, query): Filter results by event ID.

Responses

200 OK: Returns a list of play histories matching the specified criteria.
400 Bad Request: Indicates a problem with the request parameters.
401 Unauthorized: Authentication failed due to an invalid token.
500 Internal Server Error: An error occurred on the server side.

Usage

This endpoint is particularly useful for market makers who need to audit their betting activities, analyze trends, and make informed decisions based on historical data. By using the available filters, users can narrow down the results to focus on specific markets, events, or statuses, providing a comprehensive view of their play history.