Skip to main content
client.data.core.getActivity delivers a time-ordered view of wallet events. It’s perfect for portfolio dashboards, notification feeds, and audit tooling.

Request

Parameters

| Name | Type | Required | Default | Notes | | --------------- | ----------------------- | -------- | ------- | ---------------------------------------------------------------------- | ------------------ | --------------- | | user | string (address) | ✅ | – | Wallet or proxy address. | | limit | number (0–500) | | 100 | Page size. | | offset | number (0–10000) | | 0 | Page offset. | | market | string[] | | – | Condition IDs (mutually exclusive with eventId). | | eventId | number[] | | – | Event IDs (mutually exclusive with market). | | type | array of activity enums | | – | Filter by TRADE, REDEEM, MERGE, SPLIT, REWARD, CONVERSION. | | start | number (≥ 0) | | – | Unix timestamp lower bound. | | end | number (≥ 0) | | – | Unix timestamp upper bound. | | sortBy | "TIMESTAMP" | "TOKENS" | "CASH" | | "TIMESTAMP" | Sorting metric. | | sortDirection | "ASC" | "DESC" | | "DESC" | Sorting order. | | side | "BUY" | "SELL" | | – | Trade side filter. |

Response

Usage example

Failure modes

  • Missing user → validation error.
  • Conflicting filters → validation error referencing both fields.