---
title: "Get Address Related Wallets Data"
method: POST
path: "/api/v1/profiler/address/related-wallets"
tags: ["Profiler"]
---

# Get Address Related Wallets Data

`POST /api/v1/profiler/address/related-wallets`

Get wallets that are related to the input address through various types
of blockchain interactions and relationships. Returns detailed information
about each related wallet including the relationship type, transaction details, and timing information.

## Request body

- ProfilerAddressRelatedWalletsRequest
  - `address` string, required — Address to get related wallets for
  - `chain` 'arbitrum' | 'avalanche' | 'base' | 'bitcoin' | 'bnb' | 'ethereum' | 'injective' | 'iotaevm' | 'linea' | 'mantle' | 'mantra' | 'monad' | 'near' | 'optimism' | 'plasma' | 'polygon' | 'robinhood' | 'sei' | 'solana' | 'sonic' | 'starknet' | 'sui' | 'ton' | 'tron', required — Chains supported in profiler related wallets analysis.
  - `pagination` PaginationRequest — Pagination parameters for API requests.
    - `page` integer — Page number (1-based)
    - `per_page` integer — Number of records per page (max 1000)
  - `order_by` SortOrderProfilerAddressRelatedWalletsSortField[] — Custom sort order to override the endpoint's default ordering
    - `field` 'order', required — Enum for sortable fields in profiler address related wallets.
    - `direction` 'ASC' | 'DESC', required — Enum for sort directions.

## Response `200`

Address related wallets data

- ProfilerAddressRelatedWalletsResponse — Response model for profiler address related wallets endpoint. Contains the related wallets data with metadata.
  - `pagination` PaginationInfo, required — Pagination information for API responses.
    - `page` integer — Current page number
    - `per_page` integer — Number of records per page
    - `is_last_page` boolean — Whether this is the last page
  - `data` ProfilerRelatedWallet[], required — List of related wallet records
    - `address` string, required — Hexadecimal representation of the related address
    - `address_label` string — The label of the address
    - `relation` string, required — The type of relation between the address and the input address
    - `transaction_hash` string, required — Hexadecimal representation of the transaction hash
    - `block_timestamp` string, required — The timestamp of the transaction
    - `order` integer, required — The order of the relation
    - `chain` string, required — The chain of the relation

## Other responses

- `400` — Bad Request - Invalid request parameters or malformed request
- `401` — Authentication error - No API key found in request
- `402` — Payment Required - This endpoint supports pay-per-request via x402 and MPP. x402 responses advertise payment options in `Payment-Required`; MPP responses advertise a fresh `WWW-Authenticate: Payment ...` challenge. Successful MPP responses may include `Payment-Receipt`.
- `403` — Forbidden - User does not have required subscription tier or has exceeded credit limit
- `404` — Not Found - The requested resource was not found
- `422` — Validation error - Invalid request parameters
- `429` — Too Many Requests - Rate limit exceeded
- `500` — Internal Server Error - An unexpected error occurred

---

[API](https://skmtc.net/nansen/apis/nansen-api.md) · [All operations](https://skmtc.net/nansen/apis/nansen-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/nansen/nansen-api/revisions/02a4d2e7d827/schema)