Skip to main content
Security and compliance workflows combine a few signals: who an address is, where its funds came from, who it transacts with, and what contracts it touches. This guide shows the endpoints behind each signal. Labels and reputation data are inputs for your own screening rules, not screening decisions on their own. New to the API? Start with Make your first call.
Every endpoint in this guide works on all 60+ supported chains, just switch the chainid. For example, set chainid=42161 to screen the same address on Arbitrum. See Supported chains for the full list.

​
Address identity

Enrich an address with names, labels, and reputation before applying your rules.
1

Get address metadata

Retrieve Etherscan labels, names, and reputation data for an address using Etherscan Metadata.
Use labels such as Exchange, Bridge, phish-hack, and ofac-sanctioned as inputs for your own screening rules.
getaddresstag is available as a PRO endpoint on the Pro Plus plan. See PRO endpoints.
Labels and reputation data provide context for your own screening rules. Combine them with your product’s policies and risk thresholds.
2

Export label categories

For watchlist workflows, retrieve addresses by label category (e.g. ofac-sanctioned) instead of checking addresses individually.
Use getlabelmasterlist to discover available label categories.
Export label categories periodically to keep local screening data up to date.

​
Transaction monitoring

Combine address metadata with transaction data to monitor interactions with known entities.
1

Retrieve transaction activity

Track normal transactions, internal transactions, and token transfers associated with an address.
User activity can span multiple networks. Apply the same screening workflow across every supported chain you monitor.
2

Apply your screening logic

Match transaction counterparties against your labels and internal rules to surface activity that requires review.

​
Fund tracing

Understand where an address received its initial funds.
1

Find the funding source

Returns the address and transaction that first funded an EOA, an extra context signal when investigating an address. This is a PRO endpoint, available to the Standard plan and above.

​
Contract context

Understand a smart contract before your application interacts with it.
1

Check the contract source code

Verified source code and contract details for an address. Use verification status and source availability as context when evaluating a contract.
2

Retrieve the contract ABI

The ABI for a verified contract, used to decode its interactions and understand the methods it exposes.

​
Putting it together

Combine these endpoints to build common security and compliance workflows:
  • Address screening: getaddresstag labels against your rules
  • Watchlist management: exportaddresstags refreshed on a schedule
  • Transaction monitoring: txlist + txlistinternal + tokentx + labels
  • Address investigation: fundedby + transaction history
  • Contract review: getsourcecode + getabi
For multi-chain applications, repeat these workflows across each chainid where your users or contracts operate.