All requests require an API key via the
X-API-Key header.
See Authentication for details.Overview
The Wallet Activity endpoint returns on-chain earn interactions (deposits and withdrawals) for one or more wallet addresses across all opportunities and distributors. Results are ordered by date descending. This is a wallet-scoped endpoint. For distributor-scoped activity, see Distributor Activity.Endpoint
Get Wallet Activity
Comma-separated list of EVM wallet addresses. Maximum 1000 addresses per request. Addresses are case-insensitive.
Page number for pagination.
Results per page (max: 100).
Unique identifier for the interaction.
The opportunity this interaction belongs to.
Type of interaction:
deposit or withdraw.On-chain transaction hash.
Chain ID where the transaction occurred.
ISO 8601 timestamp of the on-chain transaction.
The wallet address that performed the interaction.
Human-readable token amount (already adjusted for decimals). Present when available.
USD value of the interaction at time of transaction. Present when available.
Symbol of the deposited or withdrawn token. Present when available.
URL to the token icon. Present when available.
Whether the deposit used swap mode.
Use Cases
Display Wallet Transaction History
Build a transaction history view for a user’s portfolio page.Query Multiple Wallets
Fetch activity across multiple wallets in a single request — useful for users with multiple addresses or for building aggregate views.Paginate Through All Results
Wallet Activity vs Distributor Activity
| Wallet Activity | Distributor Activity | |
|---|---|---|
| Endpoint | GET /v1/wallets/activity | GET /v1/deposit/{distributor_id} |
| Scoped by | Wallet address(es) | Distributor ID |
| Interactions | Deposits + withdrawals | Deposits only |
| Best for | Portfolio UIs, user dashboards | Distributor attribution tracking |
| Pagination | Page-based (page, hasNext) | Offset-based (offset, limit) |
Error Handling
Missing Addresses
Missing Addresses
Status Code: 400 Bad RequestSolution: Include at least one valid EVM address in the
addresses query parameter.Too Many Addresses
Too Many Addresses
Status Code: 400 Bad RequestSolution: Split your request into batches of 1000 addresses or fewer.
Request Body Sent
Request Body Sent
Status Code: 400 Bad RequestSolution: This is a GET endpoint. Remove any request body and pass parameters via the query string only.

