---
title: "Get Address Current Balance Data"
method: POST
path: "/api/v1/profiler/address/current-balance"
tags: ["Profiler"]
---

# Get Address Current Balance Data

`POST /api/v1/profiler/address/current-balance`

Retrieve current token holdings for addresses or entities. Returns detailed balance information across specified chains.

What it helps to answer:

- Current token holdings with quantities and USD valuations
- Asset distribution across different blockchain networks
- Native token versus token balances
- Stablecoin holdings and percentages
- Cross-chain portfolio composition

Note: The address field in the response will be empty if entity_name is provided.

## Request body

- ProfilerAddressBalancesRequest
  - `address` string — Address to get balances for
  - `entity_name` string — Entity name to get balances for
  - `chain` 'all' | 'arbitrum' | 'avalanche' | 'base' | 'bitcoin' | 'bnb' | 'ethereum' | 'hyperevm' | 'injective' | 'iotaevm' | 'linea' | 'mantle' | 'mantra' | 'monad' | 'near' | 'optimism' | 'plasma' | 'polygon' | 'robinhood' | 'sei' | 'solana' | 'sonic' | 'starknet' | 'sui' | 'ton' | 'tron', required — Chains supported in profiler analysis.
  - `hide_spam_token` boolean — Removes suspicious tokens from the balance list
  - `filters` ProfilerAddressBalancesFilters — Filters for profiler address current balance endpoint. These filters control which token balances are included.
    - `value_usd` NumericRangeFilter — Filter for numeric values (floats) with optional min/max bounds. Use for prices, volumes, ratios, and other decimal values. - Values between -10.5 and 100.75
      - `min` number — Minimum value (inclusive)
      - `max` number — Maximum value (inclusive)
    - `price_usd` NumericRangeFilter — Filter for numeric values (floats) with optional min/max bounds. Use for prices, volumes, ratios, and other decimal values. - Values between -10.5 and 100.75
      - `min` number — Minimum value (inclusive)
      - `max` number — Maximum value (inclusive)
    - `token_amount` IntegerRangeFilter — Filter for integer values with optional min/max bounds. Use for counts, numbers of items, and other whole number values. - Values between 5 and 100
      - `min` integer — Minimum value (inclusive)
      - `max` integer — Maximum value (inclusive)
    - `token_symbol` union — Token symbol filter
      - string
      - string[]
    - `token_address` union — Token address filter
      - string
      - string[]
    - `token_name` union — Token name filter
      - string
      - string[]
  - `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` SortOrderProfilerAddressBalancesSortField[] — Custom sort order to override the endpoint's default ordering
    - `field` 'value_usd' | 'token_symbol', required — Enum for sortable fields in profiler address balances.
    - `direction` 'ASC' | 'DESC', required — Enum for sort directions.

## Response `200`

Address current balance data

- ProfilerAddressBalancesResponse — Response model for profiler address current-balance endpoint. Contains the filtered balance 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` ProfilerBalance[], required — List of balance records
    - `chain` string, required — Chain
    - `address` string, required — Address of the wallet. Empty if entity_name is provided. EVM addresses are returned in lowercase.
    - `token_address` string, required — Address of token
    - `token_symbol` string, required — Token symbol
    - `token_name` string — Token name
    - `token_amount` number — Token balance
    - `price_usd` number — Price of the token
    - `value_usd` number — Token balance value in USD

## 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)