Unique ID that can be specified when submitting the request. The request fails if a request with the same requestId already exists.

User key encrypted with the RSA public key. Required when the key management type of the main address is co-managed (HEXLANT_MULTISIG) and the operation is signed by the main address. Not used for operations performed from a child address (e.g. NFT withdrawal from a child address).
The RSA public key is available in the developer tools of the Octet console.

Description that can be entered with the request. It is not recorded on the blockchain; it is stored only in Octet’s database.

NFT contract address

Unique ID of the NFT item. The request fails if an item with the same ID already exists. For ERC721 contracts deployed via custom deployment, this can be omitted if the INCREMENTAL feature is enabled.

URI of the NFT item. Required for ERC721, KIP17, and CW721. For ERC721 contracts deployed via custom deployment, this can be omitted if the URI_STORAGE feature is not enabled.

Address to receive the NFT item. If omitted, the item is minted to the main address.
On Ethereum- and Kaia-based platforms, the address must start with 0x and be either all lowercase or checksummed.

Sending address. Must be an address in the wallet.
Wallets of the Centralized type (CENTRALIZED) cannot use a child address as the senderAddress.

PIN of the sending address. Required if the sending address is a child address that uses a PIN.

API token