Skip to main content
POST
get_wallet_counterparties_analysis

Reading the result

The response example uses made-up values and shows selected fields. Fields vary by network and available data.
  • most_interacted, top_inflow_senders, and top_outflow_receivers each contain a counterparties result, ranked by interaction count, inbound USD volume, or outbound USD volume.
  • Each group contains up to five counterparties. The same address can appear in more than one group.
  • Check each group’s metadata for tx_derived and tx_note when the analysis uses a recent transaction sample.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
address
string
required

Wallet address to analyze on the selected network.

network
string
required

Network to query, for example ethereum. See Supported Networks for coverage.

from_date
string

Start of the requested date range, in YYYY-MM-DD format. Omit to use the default date range.

to_date
string

End of the requested date range, in YYYY-MM-DD format. Omit to use the default date range.

Response

Counterparty analysis: most-interacted + top inflow/outflow addresses for a wallet. Fields vary by network and available data. Check for status: no_data, status: error, or an error field even when HTTP status is 200. See Errors & status.

Response fields depend on the network and available data. The example shows selected fields; see Reading the result for details.