NFT

Deploy a new NFT Collection contract.

Changed on

The launch endpoint is used to deploy a new NFT Collection on the Mina blockchain. It allows users to create a new NFT Collection with customizable parameters.

post/nft/launch

Request

  • Base URL: https://minatokens.com/api/v1
  • URL: https://minatokens.com/api/v1/nft/launch
  • Auth: API key in header x-api-key

Request body

OR

Response

Successful deployment of a new NFT Collection.

senderstring required

The address initiating the transaction.

nonceinteger required

The nonce for the transaction.

memostring required

A memo for the transaction.

feenumber double required

The fee for the transaction.

proverPayloadstring required

The payload for the prover.

signedDatastring required

The signed data for the transaction.

transactionstring required

The raw transaction data.

sendTransactionboolean

Optional. Whether to broadcast the transaction after proving.

symbolstring required

The symbol of the NFT collection.

collectionNamestring required

The name of the NFT collection.

nftNamestring required

The name of the NFT.

storagestring

The storage of the NFT (IPFS hash).

privateMetadatastring

The private metadata of the NFT.

metadataRootstring

The metadata root of the NFT.

mapobject

The serialized metadata map of the NFT.

Changes

    • info

      added the new optional request property ////////////

    • info

      added the new optional request property ////////////

    • info

      added the optional property ////////////////// to the response with the status

    • info

      added the optional property ////////////////// to the response with the status

    • info

      added the optional property ////////////////// to the response with the status

    • info

      added the optional property ////////////////// to the response with the status

    • info

      added the optional property ////////////////// to the response with the status

    • info

      added the optional property ////////////////// to the response with the status

    • info

      added the optional property ////////////////// to the response with the status

    • breaking

      the response property ///////////////// became optional for the status

    • breaking

      the response property ///////////////// became optional for the status

    • breaking

      the response property ///////////// became optional for the status

    • info

      the request property /////////// became optional

    • info

      the request property /////////// became optional