Skip to main content
POST
get_wallet_deployed_contracts

Reading the result

The response example uses made-up values and shows selected fields. Fields vary by network and available data.
  • For EVM networks, data contains deployment transaction hashes, block details, and created contract addresses.
  • token_info is added when token or market data is available. An empty data array means no deployments were found in the searched history.
  • pagination.total counts the deployments found. analyzed_count is the search limit, not a confirmed count of transactions processed. Solana and Tron use different deployment fields.

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
default:ethereum

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

Response

Contracts deployed by 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.