WSP Transaction lookup
A WSP can lookup transactions based on a wallet (sub) or session-id.
Amounts
All amounts from the WLW are displayed with decimal numbers (e.g. 24.71€ = 24 Euro and 71 cents).
Transactions based on wallet (sub)
sub)Using the Get wallet transaction history endpoint, a WSP can query transactions for a given wallet.
Successful vs unsuccessful transactionsOnly successful transactions will be provided on this endpoint.
Pagination
This endpoint uses cursor-based pagination, designed to power infinite scrolling on the client side. Each response returns a bounded number of transactions to keep queries fast and payloads small.
Do not rely on a specific page size — Aera may adjust the number of returned transactions to balance between response time and user experience.
If the response includes a next parameter, more transactions are available. Pass it as a query parameter in the subsequent request to fetch the next page.
Transactions are sorted in descending order, based on when it was initiated (newest first).
Filter
Use the from and to query parameters to filter transactions by date.
Both are inclusive (full days), interpreted in timezone: CET.
If from is omitted, the endpoint returns transactions from the beginning of history. If to is omitted, it defaults to today.
The endpoint returns 400 Bad Request if to is before from.
If no transactions match the query, the response body will not include a transactions array or a next token — the fields are omitted entirely (not returned as null or []).
Pagination consistencyWhen paginating with the
nexttoken, do not change thefromortoparameters between requests. The cursor is tied to the original query range, so changing these while at the same time providing a `next` token will have no effect.
Transaction based on session-id
session-idUsing the Get wallet transaction endpoint, a WSP can query transactions based on the session-id.
The
session-idis identical to thepspReference.
Updated 3 months ago
