Mint multiple NFTs
/v3/nft/mint/batch
2 credits per API call
Create multiple NFT Tokens and transfer them to destination account. Create and transfer any NFT tokens from smart contract defined in contractAddress.
This API is supported for the following blockchains:
- BNB Smart Chain
- Celo
- Ethereum
- Harmony
- Klaytn
- KuCoin Community Chain
- Polygon
- TRON
- Flare
- Cronos
- Base
- Avalanche
- Fantom
- Optimism
This operation works in two modes. First mode works just like other NFT endpoints. Every time the funds are transferred, the transaction must be signed with the corresponding private key. No one should ever send it's own private keys to the internet because there is a strong possibility of stealing keys and loss of funds. In this method, it is possible to enter privateKey or signatureId. PrivateKey should be used only for quick development on testnet versions of blockchain when there is no risk of losing funds. In production, Tatum KMS should be used for the highest security standards, and signatureId should be present in the request. Alternatively, using the Tatum client library for supported languages. Second mode enables you to mint on any custom NFT ERC-721 smart contract, on which specified minter address is approved as a minter. You don't specify private key or signatureId, only minter address, from which the NFT will be minted.
It means you perform mint multiple NFT request with following body:
{ "to": ["0x80d8bac9a6901698b3749fe336bbd1385c1f98f2"], "url": ["ipfs://QmXJJ6UF5WkF4WTJvsdhiA1etGwBLfpva7Vr9AudGMe3pj"], "tokenId": ["9876541124516"], "contractAddress":"0x3cbb48f740595ed846abb641adfcd9f04588348d", "minter": "0x542b9ac4945a3836fd12ad98acbc76a0c8b743f5", "chain": "MATIC" }
The blockchain fee of the performed transaction is paid from the address connected with built-in private key and is debited in form of credits. The credits are debited only if NFT mint requests are performed with paid API key plan. We transform fee to the credits in accordance to the rates provided by the Tatum. If you want to batch mint on ERC-721 contract which is not deployed via Tatum API, your smart contract must contain this method:
mintMultiple(address[] to, uint256[] tokenId, string[] uri): boolean
You can use addresses specified in the bellow table to be used as a minter.
Chain
Testnet address
Mainnet Address
MATIC
0x542b9ac4945a3836fd12ad98acbc76a0c8b743f5
0xcf9e127455d28e7362380aec1b92ddee8200b295
BSC
0xc16ae5e8c985b906935a0cadf4e24f0400531883
0xcf9e127455d28e7362380aec1b92ddee8200b295
ONE
0x8906f62d40293ddca77fdf6714c3f63265deddf0
0xcf9e127455d28e7362380aec1b92ddee8200b295
ETH
0x53e8577C4347C365E4e0DA5B57A589cB6f2AB848
0xcf9e127455d28e7362380aec1b92ddee8200b295
CELO
0xBC2eBA680EE50d685cc4Fe65f102AA70AfB27D3F
0xcf9e127455d28e7362380aec1b92ddee8200b295
KLAY
0x80d8bac9a6901698b3749fe336bbd1385c1f98f2
0xcf9e127455d28e7362380aec1b92ddee8200b295
If there are not enough coins on any testnet address, feel free to send coins there.
Request
- Base URLhttps://api.tatum.io
- URLhttps://api.tatum.io/v3/nft/mint/batch
- AuthAPI key in header x-api-key
Query parameters
Specifies the testnet type. The default is ethereum-sepolia for Ethereum (ETH) currency and flare-coston for Flare (FLR) currency. Valid testnet types depend on the specified currency.
Type of testnet in query. The default type is based on the currency: ethereum-sepolia for ETH, and flare-coston for FLR. This parameter is valid only for ETH or FLR invocations with a testnet API Key. For mainnet API Key, this value is ignored. The currency/chain must be specified to determine the applicable set of testnet types.
Headers
Type of testnet in header. The default type is based on the currency: ethereum-sepolia for ETH, and flare-coston for FLR. This parameter is valid only for ETH or FLR invocations with a testnet API Key. For mainnet API Key, this value is ignored. The currency/chain must be specified to determine the applicable set of testnet types.
Request body
Example request
{
"chain": "ETH",
"to": [
"0x687422eEA2cB73B5d3e242bA5456b782919AFc85"
],
"tokenId": [
"123"
],
"minter": "0x687422eEA2cB73B5d3e242bA5456b782919AFc85",
"url": [
"https://my_token_data.com"
],
"contractAddress": "0x687422eEA2cB73B5d3e242bA5456b782919AFc85"
}Response
OK
Example response
{
"txId": "c83f8818db43d9ba4accfe454aa44fc33123d47a4f89d47b314d6748eb0e9bc9"
}Changes
No recorded changes to this operation across all 1 revision of this API.