Unique ID available to enter when requesting deployment. The request will fail when there is a duplicate requestId exists in the request.

Result of the user key being encrypted with the RSA public key. This must be entered when the key management method is set to joint management. You can find the RSA public key from the developer tool of the Octet console.

Description of the deployment that can be entered when requesting deployment. This does not involve blockchains and is recorded in Octet’s database.

NFT contract address

Unique ID of the NFT item. The request will fail when an item with the same ID exists. For ERC721 deployed in a custom deployment way, this field is not required if the INCREMENTAL feature is enabled.

URI of the NFT item. For ERC721 or KIP17 or CW721, this field must be entered. For ERC721 deployed in a custom deployment way, this field is not required if the URI_STORAGE feature is not enabled.

Address to receive the NFT item. When it is not entered, it will be minted to the main address. For Ethereum or Kaia-type platforms, the prefix is ‘0x’, and only lower case addresses and checksum addresses are available.

Sending address. This must be an address that exists in the wallet. Custodial wallets cannot set child address as a senderAddress.

Sending address PIN. This must be entered when the sending address is a child address using a PIN.

API token