For the complete documentation index, see llms.txt. Markdown versions of documentation pages are available by appending .md to page URLs.
Skip to content

Address Transactions

Data Freshness & Historical Coverage

For data freshness and historical coverage, see Data Coverage by Chain; this endpoint follows it.

Entity transaction lookups

To retrieve transactions across an entity's wallets, provide entity_name instead of address. Provide exactly one of these fields. Use an existing entity name, such as Vitalik Buterin.

Specify a short date window with from and to for entity requests. Date-only bounds include the whole UTC end day. Ranges exceeding the supported limit return HTTP 422. Individual-wallet requests retain their existing date limits.

The endpoint rejects these entity classifications, including classifications inherited from an alias's main entity:

Excluded category
Classifications

Exchanges

CEX, DEX

Blockchain networks

Blockchain, Layer 1, Layer 2, Scaling

Staking and validators

Staking, Validator, BSC Validator, Node Operator, Liquid Staking

DeFi

DeFi

These restrictions are conservative because aggregate transaction volume can exceed the response budget even within short date windows. They exclude some entities whose observed queries succeeded. Eligibility follows current entity classifications; entities without classifications remain eligible and do not guarantee a fast response. If entity eligibility verification is unavailable, the request returns HTTP 503 without running the transaction lookup.

Certain entities are also rejected due to their high transaction volumes, on every chain including chain: "all". These requests return HTTP 422 before the transaction lookup runs. The error identifies the unsupported entity and recommends querying an individual wallet with address instead. Matching ignores letter case and leading or trailing whitespace.

This restriction applies only to entity_name on /api/v1/profiler/address/transactions. You can still query restricted entities' individual wallets with address, use them in counterparty filters, and use entity lookups on other endpoints.

chain: "all" remains supported for eligible entities. The existing page-size limit of 100 and normal API limits still apply. Aliases inherit both category exclusions and measured exclusions of their main entity.

Requests for supported entities can still be slow or time out. For faster responses, specify a date range or a single chain. If a request times out, retry with a narrower date range.

For example:

{
  "entity_name": "Vitalik Buterin",
  "chain": "all",
  "date": {"from": "2026-09-01", "to": "2026-09-07"},
  "pagination": {"page": 1, "per_page": 20}
}

Get Address Transactions Data

post

Retrieve recent blockchain transactions for an address or existing entity, including token transfers and native currency movements. Provide exactly one of address or entity_name. Entity lookups combine transactions across the entity's wallets and support date windows of at most seven days; chain="all" includes all supported chains. Entities classified as CEX, DEX, Blockchain, Layer 1, Layer 2, Scaling, Staking, Validator, BSC Validator, Node Operator, Liquid Staking or DeFi are excluded, as are entities with confirmed timeout evidence. Exclusions apply to aliases too. Unsupported entities return HTTP 422. Missing classifications remain eligible; the restrictions do not guarantee latency. If entity eligibility verification is unavailable, the request returns HTTP 503.

Authorizations
apikeystringRequired

API key for authentication

Body
addressany ofOptional

Address to get transactions for. Provide either address or entity_name.

Example: 0x28c6c06298d514db089934071355e5743bf21d60
stringOptional
entity_nameany ofOptional

Existing entity name to get transactions for. Provide either entity_name or address. Certain high-volume entities are unsupported on every chain. These entity lookups return HTTP 422. Use address for an individual wallet instead. Entities with these classifications are also unsupported: BSC Validator, Blockchain, CEX, DEX, DeFi, Layer 1, Layer 2, Liquid Staking, Node Operator, Scaling, Staking, Validator. Aliases inherit their main entity's exclusions. Even supported entities can time out; narrow the date range if this happens.

Example: Vitalik Buterin
stringOptional
chainstring · enumRequired

Blockchain chain for the transactions

Example: ethereumPossible values:
hide_spam_tokenbooleanOptional

Removes suspicious tokens from the transaction list

Default: trueExample: true
filtersany ofOptional

Additional filters to apply. Only filters for columns that are being selected will be applied.

Example: {"volume_usd":{"min":100}}
order_byany ofOptional

Custom sort order to override the endpoint's default ordering

Responses
200

Address transaction data

application/json
post/api/v1/profiler/address/transactions
POST /api/v1/profiler/address/transactions HTTP/1.1
Host: api.nansen.ai
apikey: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 331

{
  "address": "0x28c6c06298d514db089934071355e5743bf21d60",
  "entity_name": "Vitalik Buterin",
  "chain": "ethereum",
  "date": {
    "from": "2025-08-01T00:00:00Z",
    "to": "2025-08-10T23:59:59Z"
  },
  "hide_spam_token": true,
  "filters": {
    "volume_usd": {
      "min": 100
    }
  },
  "pagination": {
    "page": 1,
    "per_page": 20
  },
  "order_by": [
    {
      "field": "block_timestamp",
      "direction": "ASC"
    }
  ]
}
{
  "pagination": {
    "page": 1,
    "per_page": 10,
    "is_last_page": true
  },
  "data": [
    {
      "chain": "text",
      "method": "text",
      "tokens_sent": [
        {
          "token_symbol": "text",
          "token_amount": 1,
          "price_usd": 1,
          "value_usd": 1,
          "token_address": "text",
          "chain": "text",
          "from_address": "text",
          "to_address": "text",
          "from_address_label": "text",
          "to_address_label": "text"
        }
      ],
      "tokens_received": [
        {
          "token_symbol": "text",
          "token_amount": 1,
          "price_usd": 1,
          "value_usd": 1,
          "token_address": "text",
          "chain": "text",
          "from_address": "text",
          "to_address": "text",
          "from_address_label": "text",
          "to_address_label": "text"
        }
      ],
      "volume_usd": 1,
      "block_timestamp": "text",
      "transaction_hash": "text",
      "source_type": "text"
    }
  ]
}

Get Transaction with Token Transfer Lookup Data

post

Get comprehensive transaction information including token transfers and NFT transfers. This endpoint provides detailed information about a specific transaction including native cryptocurrency movements, token transfers, and NFT transfers with USD values.

Authorizations
apikeystringRequired

API key for authentication

Body
chainstring · enumRequired

Blockchain chain for the transaction lookup

Example: ethereumPossible values:
transaction_hashstringRequired

Transaction hash to lookup. The format depends on the chain: EVM chains and 'all' take a 0x-prefixed 64-character hex string; bitcoin, tron and injective take a 64-character hex string with or without the 0x prefix; starknet takes a 0x-prefixed hex string of up to 64 characters; sui and near take the base58 transaction digest. Hex hashes are case-insensitive.

Example: 0xf16f93cb53f4f977d45b1b08af7b66e1939d0fe69d669012458239b23797e492
block_timestampany ofOptional

Timestamp of the transaction block in 'YYYY-MM-DD HH:MM:SS' format (UTC). ISO 8601 forms such as '2025-08-06T01:47:11Z' are also accepted; a time with an offset is converted to UTC. Optional for most EVM chains — resolved automatically when omitted. Required for non-EVM chains (bitcoin, tron, ton, starknet, sui, near), and for an injective hash sent without the 0x prefix.

Example: 2025-08-06 01:47:11
stringOptional
Responses
200

Transaction lookup data with token and NFT transfer information

application/json
post/api/v1/transaction-with-token-transfer-lookup
POST /api/v1/transaction-with-token-transfer-lookup HTTP/1.1
Host: api.nansen.ai
apikey: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 148

{
  "chain": "ethereum",
  "transaction_hash": "0xf16f93cb53f4f977d45b1b08af7b66e1939d0fe69d669012458239b23797e492",
  "block_timestamp": "2025-08-06 01:47:11"
}
{
  "data": [
    {
      "chain": "text",
      "transaction_hash": "text",
      "from_address": "text",
      "from_address_label": "text",
      "to_address": "text",
      "to_address_label": "text",
      "native_value": 1,
      "dated_native_price": 1,
      "dated_native_value_usd": 1,
      "current_native_price": 1,
      "current_native_value_usd": 1,
      "receipt_status": 1,
      "block_timestamp": "text",
      "token_transfer_array": [
        {
          "from_address": "text",
          "from_address_label": "text",
          "to_address": "text",
          "to_address_label": "text",
          "token_address": "text",
          "token_symbol": "text",
          "token_amount": 1,
          "dated_price_usd": 1,
          "dated_value_usd": 1,
          "current_price_usd": 1,
          "current_value_usd": 1,
          "transfer_id": "text"
        }
      ],
      "nft_transfer_array": [
        {
          "from_address": "text",
          "from_address_label": "text",
          "to_address": "text",
          "to_address_label": "text",
          "project_id": "text",
          "collection_name": "text",
          "nft_id": "text"
        }
      ]
    }
  ]
}

Last updated

Was this helpful?