Skip to main content
POST
/
v0
/
platform
/
assets
curl --request POST \
  --url https://api.blockaid.io/v0/platform/assets \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <api-key>' \
  --data '
{
  "identifier_type": "address",
  "identifier": "0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef",
  "tags": [
    "example"
  ],
  "alias": "bluefin",
  "runtime": "sui",
  "chain_name": "mainnet"
}
'
"<any>"

Authorizations

​
X-API-Key
string
header
required

Body

application/json
​
identifier
string
required

The address identifier of the asset.

​
runtime
enum<string>
required

The runtime of the hosting chain. The runtime name

Available options:
evm,
sui
​
chain_name
enum<string>
required

The chain where the asset resides in. The chain name

Available options:
arbitrum,
avalanche,
base,
bsc,
ethereum,
optimism,
polygon,
ethereum-sepolia,
gnosis,
soneium-minato,
abstract,
soneium,
mainnet
​
identifier_type
enum<string>
default:address
Available options:
address
​
tags
string[]

Group your assets by tags to filter by them.

​
alias
string

Use an alias to easily identify this asset across the platform. The asset chip will show the alias rather than the raw identifier.

​
contract_interface
ContractInterface · object[]

The contract interfaces for the asset (for evm the ABI file). If the asset is a proxy, include the implementation contract interface as well. Will be auto-fetched if not provided.

Response

Asset created successfully

The response is of type any.