Create NFT Collection
curl --request POST \
  --url https://testnet.walletkit.com/nfts/collections \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "network": "Ethereum",
  "name": "<string>",
  "symbol": "<string>",
  "image_url": "<string>",
  "base_uri": "<string>",
  "developer_secret": "<string>",
  "user_pin": "<string>"
}'
{
  "transaction_id": "<string>",
  "network": "Ethereum",
  "status": "<string>"
}

​
Headers

​
X-WalletKit-Project-ID
string
required
Your WalletKit Project ID can be found on the API Keys page in the WalletKit Dashboard.

Authorizations

​
Authorization
string
header
required

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

Body

application/json
​
network
enum<string>
required
Available options:
Ethereum,
Polygon,
Base,
Avalanche,
Polkadot,
Vara
​
name
string
required

collection name

​
symbol
string
required

Collection symbol used for identification purposes

​
image_url
string
required

URL to the collection logo image

​
base_uri
string | null

Base URI for computing tokenURI which resolves to token metadata JSON. If set, the resulting URI for each token will be the concatenation of the baseURI and the tokenId (or tokenURI if tokenURI is set when minting the NFT).

​
developer_secret
string | null

On testnet, the developer_secret is always "testnet-secret". On mainnet, the developer_secret is set by the developer during account activation.

​
user_pin
string | null

A 6-digit numeric pin that is only known to the user, set during wallet creation. This pin is required to sign transactions from this wallet.

Response

​
transaction_id
string
required
​
network
enum<string>
required
Available options:
Ethereum,
Polygon,
Base,
Avalanche,
Polkadot,
Vara
​
status
string
required