Skip to main content
All requests require an API key via the X-API-Key header. See Authentication for details.

Overview

GET /v2/wallets/activity/ 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. To pick between the three views (positions, wallet activity, distributor activity), see the Portfolio & Activity overview.

Endpoint

Get Wallet Activity

Query Parameters
string
required
Comma-separated list of EVM wallet addresses. Maximum 1000 addresses per request. Addresses are case-insensitive.
integer
default:"1"
Page number for pagination.
integer
default:"20"
Results per page (max: 100).
This is a GET endpoint. Pass all parameters in the query string; do not send a request body.

Response Example

Response Fields

array
Array of activity items. Each item uses the same activity-item shape as the deposit items returned by Distributor Activity, with one difference: interaction is deposit or withdraw here, where the distributor endpoint always returns deposit.
string
Type of interaction. One of deposit or withdraw.
object
Pagination metadata. Same shape as the pagination object on Distributor Activity.
integer
Current page number.
integer
Results per page.
integer
Total number of matching interactions.
integer
Total number of pages.
boolean
Whether a next page exists.
boolean
Whether a previous page exists.

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

Error Handling

Status Code: 400 Bad Request
Solution: Include at least one valid EVM address in the addresses query parameter.
Status Code: 400 Bad Request
Solution: Split your request into batches of 1000 addresses or fewer.
Status Code: 400 Bad RequestSolution: This is a GET endpoint. Remove any request body and pass parameters via the query string only.