Mass Minting

Intro

Mass Minting allows you to mint a huge number of NFTs. You don't need to wait for the entire minting process to be completed before getting your response

This enhancement eradicates the risk of timeouts or lost connections arising from prolonged processing times or fluctuating gas fees. If a minting attempt fails, Quantum will automatically resubmit the request, minimizing interruptions.

Mass Minting provides a substantial increase in throughput for NFT minting, guaranteeing you a quicker and smoother NFT-minting experience.

You can submit a token-type creation request or an NFT mint request and then track its status using a unique ID.

Mass Minting Endpoints

We have introduced four new endpoints for Mass Minting. These endpoints can be used to:

Prerequisites

📘

You can skip this part if you have a contract created through NFT v1. Make sure you have the contractAddress and secretType as they will be used in the create Token-type request.

1. Create a contract/collection

This endpoint is used to create a contract/collection on v2.

Request Endpoint: reference

HTTP

Example Request

HTTP

JSON

Response Body

📘

The result.id is the deploymentId and can be used to track the status of this contract creation request.

JSON

2. Check the status of the contract/collection

This endpoint is used to check the status of a contract/collection on v2. The {deploymentId} in the path is for tracking the status of contract creation. It is in the response body of the create contract/collection endpoint as result.id.

Request Endpoint: reference

HTTP

Example Request

HTTP

Response Body

📘

In the response body look for the result.status parameter. It can have three possible values:

  • SUCCEEDED

  • PENDING

  • FAILED

JSON

Mass Minting Endpoints

1. Create a token-type

This endpoint is used to create a token-type and it accepts the request body parameters as an ARRAY.

The contractAddress and secretType (blockchain) is defined within the request body.

Request Endpoint: reference

HTTP

Example Request

HTTP

JSON

Response Body

📘

The result.creations.id is the creationId and can be used to track the status of this token-creation request.

JSON

2. Check the status of token-type

This endpoint is used to check the status of token-type creation. The {creationId} in the path is for tracking the status of token-type creation. It is in the response body of the create token-type endpoint as result.id.

Request Endpoint: reference

HTTP

Example Request

HTTP

Response Body

📘

In the response body look for the result.status parameter. It can have three possible values:

  • SUCCEEDED

  • PENDING

  • FAILED

JSON

3. Mint NFTs

This endpoint is used to mint fungible or non-fungible tokens to wallet addresses. You can add multiple addresses as shown below. This is the capability of mass minting, you can mint multiple tokens to multiple wallet addresses simultaneously.

📘

NOTE: The contractAddress, secretType (blockchain), and the tokenTypeId are defined in the request body.

Request Endpoint: reference

HTTP

Example Request

HTTP

JSON

Response Body

📘

The result.mints.id is the mintId and can be used to track the status of this NFT mint request.

JSON

4. Check the status of NFT mints

This endpoint is used to check the status of NFT mints. The {mintId} in the path is for tracking the status of the NFT mint. It is in the response body of the Mint Fungible or Non-Fungible Tokens endpoint as result.mints.id.

Request Endpoint: reference

HTTP

Example Request

HTTP

Response Body

📘

In the response body look for the result.status parameter. It can have three possible values:

  • SUCCEEDED

  • PENDING

  • FAILED

JSON

Last updated