---
title: "List chains where a wallet or contract has on-chain activity"
method: POST
path: "/?ankr_getInteractions"
tags: ["Query API"]
---

# List chains where a wallet or contract has on-chain activity

`POST /?ankr_getInteractions`

## Request

- Base URL: `https://rpc.ankr.com/multichain/569ca1f392f7d3d0bb1073a1173ecb649af1d9249231fe59fa95db19d5ae41fe`
- URL: `https://rpc.ankr.com/multichain/569ca1f392f7d3d0bb1073a1173ecb649af1d9249231fe59fa95db19d5ae41fe/?ankr_getInteractions`
- Auth: none declared
- TypeScript: <https://skmtc.dev/ankr/apis/ankr-advanced-api/docs/%3Fankr_getInteractions/post.ts> (a function with typed inputs; its response is checked against the schema)

Returns the set of supported blockchains on which the given address has any indexed activity — tokens, NFTs, or transactions. Useful for cross-chain wallet dashboards or address-lookup UIs that want to avoid hitting every chain.

Pass a single `address` (wallet or contract). The response is a string array of chain identifiers; pair with downstream calls (e.g. `ankr_getAccountBalance`, `ankr_getTransactionsByAddress`) for the actual data.

Part of the **Query API** product (700 compute units per call, $0.00007 at base rate).

## Request body

- object
  - `id` integer, required: Client-supplied request ID echoed in the response.
  - `jsonrpc` '2.0', required
  - `method` 'ankr_getInteractions', required
  - `params` object, required
    - `address` string, required: Wallet or contract address.

## Response `200`

Success. JSON-RPC `result` contains the `blockchains` array. JSON-RPC errors are returned with HTTP 200; check the response body for an `error` key.

- object
  - `id` integer, required
  - `jsonrpc` '2.0', required
  - `result` object, required
    - `blockchains` string[], nullable, required: Chains on which the address has indexed activity.

## Other responses

- `400`: Bad Request — malformed JSON-RPC envelope or invalid `params`. The gateway rejects before the JSON-RPC layer processes the call.
- `401`: Unauthorized — missing or invalid API key in the server URL path. Verify that `{API_KEY}` is set to a valid project key.
- `429`: Too Many Requests — the API key has exceeded its rate or quota limits. Back off and retry; consider upgrading the Premium tier for higher limits.
- `500`: Server error — unexpected condition. Retry with exponential backoff; if it persists, file a ticket at https://www.ankr.com/support/.

---

[API](https://skmtc.dev/ankr/apis/ankr-advanced-api.md) - [All operations](https://skmtc.dev/ankr/apis/ankr-advanced-api/llms.txt) - [OpenAPI document](https://skmtc.dev/ankr/apis/ankr-advanced-api/revisions/77e494aeec1b?raw)