Get Transaction History
Get transaction history for a player. Up to 50 Events can be returned at once (or 250 with response compression enabled). You can use continuation tokens to paginate through results that return greater than the limit. Getting transaction history has a lower RPS limit than getting a Player’s inventory with Player Entities having a limit of 30 requests in 300 seconds.
Allowed entity token types: title, master_player_account, title_player_account
Authorizations
This API requires an Entity Session Token, available from the Entity GetEntityToken method.
Body
Get transaction history for specified entity and collection.
Get transaction history for specified entity and collection.
Number of items to retrieve. This value is optional. The default value is 10. The maximum value is 50, or 250 if response compression is enabled.
The id of the entity's collection to perform this action on. (Default="default")
An opaque token used to retrieve the next page of items, if any are available. Should be null on initial request.
The optional custom tags associated with the request (e.g. build number, external trace identifiers, etc.).
The entity to perform this action on.
An OData filter used to refine the TransactionHistory. Transaction properties 'timestamp', 'transactionid', 'apiname' and 'operationtype' can be used in the filter. Properties 'transactionid', 'apiname', and 'operationtype' cannot be used together in a single request. The 'timestamp' property can be combined with 'apiname' or 'operationtype' in a single request. For example: "timestamp ge 2023-06-20T23:30Z" or "transactionid eq '10'" or "(timestamp ge 2023-06-20T23:30Z) and (apiname eq 'AddInventoryItems')". By default, a 6 month timespan from the current date is used.
An OData orderby to order TransactionHistory results. The only supported values are 'timestamp asc' or 'timestamp desc'. Default orderby is 'timestamp asc'
