v1
latestOpenAPI 3.0.02026-07-23187.1 KBRetrieve Transactions
If multiple member filters are included, only one will be used. If multiple are passed the following order precedence will be used: playerId -> memberId -> providerId -> code.<br/><br/>NOTE: This method uses private authentication API keys and should never be called from or embedded into the gaming client. These routes should ONLY be accessed from your back-end services.
Query parameters
Group to retrieve transactions for
Maximum number of records to return
Cursor for the page of transactions to be returned. Changing query parameters when using a cursor will result in an error.
Page of records to return. Not recommended, as it disables cursor pagination when specified.
NOTE: Start Date should be in UTC
NOTE: End Date should be in UTC
Origin(s) to include.
Transaction statuses to include.
Filter transactions by creator code
Only used when code filtering is used. Member scope will return all transactions for the member associated with the specified code (even if they have multiple codes). Code scope will return only transactions with the specified code.
Filter by member ID
Filter by your internal user/player ID for this member
Filter a member with a specific OAUTH provider ID, such as twitch or youtube
Property and sort direction. Format: { property }:{ asc or desc }. Valid properties: transactionDate.
Response
Returns all transactions within the specified filters