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)

Using the Get wallet transaction history endpoint, a WSP can query transactions for a given wallet.

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).

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 []).

Time zones

The zoneId parameter determines how the from and to date filters are interpreted. Since dates have no time component, zoneId controls where the day boundary falls.

For example, a transaction at 23:30 UTC on Jan 15th is still Jan 15th when zoneId=America/New_York, but already Jan 16th when zoneId=Asia/Tokyo`.

Accepts short IDs (CET, UTC, GMT), region-based IDs (Europe/Brussels, America/New_York), or UTC offsets (+02:00, -05:00).

Transaction based on session-id

Using the Get wallet transaction endpoint, a WSP can query transactions based on the session-id.