Cursor-paginated activity feed for a user (v2)
Path parameters
Query parameters
Page size. Default 25, clamped to 100.
Opaque cursor from the previous page’s meta.nextCursor. Omit for the first page.
Action types, comma-separated or repeated (e.g. type=CONVERT,BRIDGE)
Statuses, comma-separated or repeated. All statuses are served when omitted.
Chain ids, comma-separated or repeated. Matches the source or destination chain, so a settled bridge is found from both ends.
Registry asset keys, comma-separated or repeated (e.g. assetKey=usd-coin,cbbtc). Values are OR-ed within the parameter and AND-ed with every other filter. Unknown keys are rejected with a 400 by the query service — existence needs the database, so it cannot be checked here.
Registry asset keys, comma-separated or repeated. Unlike assetKey (OR-ed: any leg matches), the action’s entire set of input/output assets must equal exactly this set — order-independent, chain-independent (USDC on Arbitrum and USDC on Base are the same asset), fee legs ignored. An action with a leg the registry cannot resolve never matches: it cannot be proven to be this pair. Composes with every other filter, including assetKey. Unknown keys are rejected with a 400 by the query service.
Inclusive lower bound on occurredAt (Unix seconds)
Inclusive upper bound on occurredAt (Unix seconds)
Response
Feed page, newest first, with meta.nextCursor (null on the last page)