/* istanbul ignore file */ /* tslint:disable */ /* eslint-disable */ import type { AddNftMinter } from '../models/AddNftMinter'; import type { AddNftMinterKMS } from '../models/AddNftMinterKMS'; import type { AlgorandMintedResult } from '../models/AlgorandMintedResult'; import type { BurnNft } from '../models/BurnNft'; import type { BurnNftCelo } from '../models/BurnNftCelo'; import type { BurnNftFlowKMS } from '../models/BurnNftFlowKMS'; import type { BurnNftFlowMnemonic } from '../models/BurnNftFlowMnemonic'; import type { BurnNftFlowPK } from '../models/BurnNftFlowPK'; import type { BurnNftKMS } from '../models/BurnNftKMS'; import type { BurnNftKMSCelo } from '../models/BurnNftKMSCelo'; import type { BurnNftKMSTron } from '../models/BurnNftKMSTron'; import type { BurnNftTron } from '../models/BurnNftTron'; import type { CeloTx } from '../models/CeloTx'; import type { DeployNft } from '../models/DeployNft'; import type { DeployNftCelo } from '../models/DeployNftCelo'; import type { DeployNftCeloKMS } from '../models/DeployNftCeloKMS'; import type { DeployNftFlowKMS } from '../models/DeployNftFlowKMS'; import type { DeployNftFlowMnemonic } from '../models/DeployNftFlowMnemonic'; import type { DeployNftFlowPK } from '../models/DeployNftFlowPK'; import type { DeployNftKMS } from '../models/DeployNftKMS'; import type { DeployNftTron } from '../models/DeployNftTron'; import type { DeployNftTronKMS } from '../models/DeployNftTronKMS'; import type { EthTx } from '../models/EthTx'; import type { FlowMintedMultipleResult } from '../models/FlowMintedMultipleResult'; import type { FlowMintedResult } from '../models/FlowMintedResult'; import type { FlowTx } from '../models/FlowTx'; import type { MintMultipleNft } from '../models/MintMultipleNft'; import type { MintMultipleNftCelo } from '../models/MintMultipleNftCelo'; import type { MintMultipleNftFlowKMS } from '../models/MintMultipleNftFlowKMS'; import type { MintMultipleNftFlowMnemonic } from '../models/MintMultipleNftFlowMnemonic'; import type { MintMultipleNftFlowPK } from '../models/MintMultipleNftFlowPK'; import type { MintMultipleNftKMS } from '../models/MintMultipleNftKMS'; import type { MintMultipleNftKMSCelo } from '../models/MintMultipleNftKMSCelo'; import type { MintMultipleNftKMSTron } from '../models/MintMultipleNftKMSTron'; import type { MintMultipleNftMinter } from '../models/MintMultipleNftMinter'; import type { MintMultipleNftTron } from '../models/MintMultipleNftTron'; import type { MintNft } from '../models/MintNft'; import type { MintNftAlgorand } from '../models/MintNftAlgorand'; import type { MintNftAlgorandKMS } from '../models/MintNftAlgorandKMS'; import type { MintNftCelo } from '../models/MintNftCelo'; import type { MintNftExpress } from '../models/MintNftExpress'; import type { MintNftExpressAlgorand } from '../models/MintNftExpressAlgorand'; import type { MintNftExpressSolana } from '../models/MintNftExpressSolana'; import type { MintNftFlowKMS } from '../models/MintNftFlowKMS'; import type { MintNftFlowMnemonic } from '../models/MintNftFlowMnemonic'; import type { MintNftFlowPK } from '../models/MintNftFlowPK'; import type { MintNftKMS } from '../models/MintNftKMS'; import type { MintNftKMSCelo } from '../models/MintNftKMSCelo'; import type { MintNftKMSTron } from '../models/MintNftKMSTron'; import type { MintNftMinter } from '../models/MintNftMinter'; import type { MintNftSolana } from '../models/MintNftSolana'; import type { MintNftSolanaKMS } from '../models/MintNftSolanaKMS'; import type { MintNftTron } from '../models/MintNftTron'; import type { NftTx } from '../models/NftTx'; import type { SignatureId } from '../models/SignatureId'; import type { SolanaMintedResult } from '../models/SolanaMintedResult'; import type { TransactionHash } from '../models/TransactionHash'; import type { TransferNft } from '../models/TransferNft'; import type { TransferNftAlgo } from '../models/TransferNftAlgo'; import type { TransferNftAlgoExpress } from '../models/TransferNftAlgoExpress'; import type { TransferNftAlgoKMS } from '../models/TransferNftAlgoKMS'; import type { TransferNftCelo } from '../models/TransferNftCelo'; import type { TransferNftFlowKMS } from '../models/TransferNftFlowKMS'; import type { TransferNftFlowMnemonic } from '../models/TransferNftFlowMnemonic'; import type { TransferNftFlowPK } from '../models/TransferNftFlowPK'; import type { TransferNftKMS } from '../models/TransferNftKMS'; import type { TransferNftKMSCelo } from '../models/TransferNftKMSCelo'; import type { TransferNftKMSTron } from '../models/TransferNftKMSTron'; import type { TransferNftSolana } from '../models/TransferNftSolana'; import type { TransferNftSolanaKMS } from '../models/TransferNftSolanaKMS'; import type { TransferNftTron } from '../models/TransferNftTron'; import type { UpdateCashbackValueForAuthorNft } from '../models/UpdateCashbackValueForAuthorNft'; import type { UpdateCashbackValueForAuthorNftCelo } from '../models/UpdateCashbackValueForAuthorNftCelo'; import type { UpdateCashbackValueForAuthorNftKMS } from '../models/UpdateCashbackValueForAuthorNftKMS'; import type { UpdateCashbackValueForAuthorNftKMSCelo } from '../models/UpdateCashbackValueForAuthorNftKMSCelo'; import type { UpdateCashbackValueForAuthorNftKMSTron } from '../models/UpdateCashbackValueForAuthorNftKMSTron'; import type { UpdateCashbackValueForAuthorNftTron } from '../models/UpdateCashbackValueForAuthorNftTron'; import type { VerifySolanaNFT } from '../models/VerifySolanaNFT'; import type { VerifySolanaNFTKMS } from '../models/VerifySolanaNFTKMS'; import type { CancelablePromise } from '../core/CancelablePromise'; import { request as __request } from '../core/request'; export class NftErc721OrCompatibleService { /** * Deploy an NFT smart contract *
100 credits per API call on Flow
* 2 credits per API call on the other blockchains
Deploy an NFT smart contract on the blockchain. In a deployed NFT smart contract, you can mint NFTs (one NFT at a time or multiple NFTs at once), burn, and transfer NFTs.
* Smart contracts are standardized and audited.
This API is supported for the following blockchains:
*By default, an NFT smart contract is deployed as a general ERC-721 smart contract compatible with OpenSea royalties. This is a standard ERC-721 contract with AccessControl and Ownable, enhanced with NFT batch minting. NFTs minted in this smart contract are compatible with OpenSea and its royalty structure.
*
In addition to the general ERC-721 contract, you can also deploy the following types of NFT smart contracts for the supported blockchains except for Flow and TRON:
*
cashback parameter set to true in the request body.provenance parameter set to true in the request body.You can enable public minting for cashback and provenance smart contracts. By default, public minting is disabled, which means that only the blockchain address whose private key was used to create the smart contract or the blockchain addresses added to the smart contract as NFT minters will be able to mint NFTs for the contract. To enable public minting and allow anyone to mint NFTs on top of the smart contract, deploy the contract with the publicMint parameter set to true in the request body.
You can review the code of a deployed NFT smart contract here (if the contract is deployed on Flow) or here (if the contract is deployed on any other supported blockchain).
*Signing a transaction
*When deploying an NFT smart contract, you are charged a fee for the transaction, and you must sign the transaction with the private key of the blockchain address from which the fee will be deducted.
*Providing the private key in the API is not a secure way of signing transactions, because the private key can be stolen or exposed. Your private keys should never leave your security perimeter. You should use the private keys only for testing a solution you are building on the testnet of a blockchain.
*For signing transactions on the mainnet, we strongly recommend that you use the Tatum Key Management System (KMS) and provide the signature ID instead of the private key in the API. Alternatively, you can use the Tatum JavaScript client.
* * @param requestBody * @param xTestnetType Type of Ethereum testnet. Defaults to Sepolia. Valid only for ETH invocations for testnet API Key. For mainnet API Key, this value is ignored. * @returns any OK * @throws ApiError */ public static nftDeployErc721( requestBody: (DeployNft | DeployNftCelo | DeployNftTron | DeployNftKMS | DeployNftCeloKMS | DeployNftTronKMS | DeployNftFlowPK | DeployNftFlowMnemonic | DeployNftFlowKMS), xTestnetType: 'ethereum-sepolia' = 'ethereum-sepolia', ): CancelablePromise<(TransactionHash | SignatureId)> { return __request({ method: 'POST', path: `/v3/nft/deploy`, headers: { 'x-testnet-type': xTestnetType, }, body: requestBody, mediaType: 'application/json', errors: { 400: `Bad Request. Validation failed for the given object in the HTTP Body or Request parameters.`, 401: `Unauthorized. Not valid or inactive subscription key present in the HTTP Header.`, 403: `Forbidden. The request is authenticated, but it is not possible to required perform operation due to logical error or invalid permissions.`, 500: `Internal server error. There was an error on the server during the processing of the request.`, }, }); } /** * Mint an NFT *100 credits per API call on Flow
* 2 credits per API call on the other blockchains
You can mint NFTs using either of the following methods:
* *NFT Express is Tatum's feature that helps you mint NFTs easier than minting natively on a blockchain.
*With NFT Express, you can choose whether to mint NFTs on the pre-built NFT smart contract provided by Tatum or on your own smart contract.
*If you want to mint NFTs using the pre-built smart contract, you do not need to deploy your own NFT smart contract. You do not need to provide the address of the NFT smart contract and the token ID in the request body either. The address of the smart contract and the token ID are provided automatically by Tatum.
The token ID is autogenerated. It starts with 0 and is increased by 1 for each new NFT. The token ID is calculated separately for each supported blockchain and its mainnet and testnet.
You can mint NFTs on the pre-built smart contract provided by Tatum on the following blockchains:
*Depending on what blockchain you use, choose the request body schema to use in the API call.
*MintNftExpress schema of the request body.MintNftExpressAlgorand schema of the request body.transferNftAlgoExpress schema of the request body).MintNftExpressSolana schema of the request body.to parameter of the request body). This address is returned in the nftAccountAddress parameter in the response body, is owned by the recipient's address, and has the same private key.nftAddress parameter.transferNftSolana or transferNftSolanaKMS schema of the request body). In the request body:
* contractAddress parameter to the address from the nftAddress parameter in the response body of the minting call.from and to parameters to the recipient's address from the to parameter in the response body of the minting call.If you want to mint NFTs using your own smart contract, you are going to use an NTF minter, a special blockchain address provided by Tatum that will cover the minting fees. The number of credits equivalent to the fees will be then deducted from the monthly credit allowance of your paid pricing plan.
*
You can mint NFTs on your own smart contract on the following blockchains:
*To mint NFTs using your own smart contract, do the following:
*MintNftMinter schema of the request body.chain is the blockchain that you use.to is the blockchain address where to send the minted NFT to.url is the URL of the NFT metadata.minter is the address of the NFT minter that you found in Step 1.contractAddress is the address of your NFT smart contract.tokenId is the the token ID of the NFT.
* {
* "chain": "CELO",
* "to": "0x8ce4e40889a13971681391aad29e88efaf91f784",
* "url": "ipfs://QmXJJ6UF5WkF4WTJvsdhiA1etGwBLfpva7Vr9AudGMe3pj",
* "contractAddress": "0x687422eEA2cB73B5d3e242bA5456b782919AFc85",
* "tokenId": "0123",
* "minter": "0xBC2eBA680EE50d685cc4Fe65f102AA70AfB27D3F"
* }
*
* When you make an API call with this request body, the private key of the NFT minter will be added to the request body automatically:
*
* {
* "chain": "CELO",
* "to": "0x8ce4e40889a13971681391aad29e88efaf91f784",
* "url": "ipfs://QmXJJ6UF5WkF4WTJvsdhiA1etGwBLfpva7Vr9AudGMe3pj",
* "contractAddress": "0x687422eEA2cB73B5d3e242bA5456b782919AFc85",
* "tokenId": "0123",
* "minter": "0xBC2eBA680EE50d685cc4Fe65f102AA70AfB27D3F",
* "fromPrivateKey": "0x05e150c73f1920ec14caa1e0b6aa09940899678051a78542840c2668ce5080c2"
* }
*
* The following table lists the blockchain addresses of the Tatum NFT minters for the testnet and mainnet of the supported blockchains:
*| Blockchain | *Minter address - testnet* | *Minter address - mainnet | *
|---|---|---|
| BNB Smart Chain | *0xc16ae5e8c985b906935a0cadf4e24f0400531883 | *0x49678AAB11E001eb3cB2cBD9aA96b36DC2461A94 | *
| Celo | *0xBC2eBA680EE50d685cc4Fe65f102AA70AfB27D3F | *0x49678AAB11E001eb3cB2cBD9aA96b36DC2461A94 | *
| Ethereum | *0x53e8577C4347C365E4e0DA5B57A589cB6f2AB848 | *0x49678AAB11E001eb3cB2cBD9aA96b36DC2461A94 | *
| Harmony | *0x8906f62d40293ddca77fdf6714c3f63265deddf0 | *0x49678AAB11E001eb3cB2cBD9aA96b36DC2461A94 | *
| Klaytn | *0x80d8bac9a6901698b3749fe336bbd1385c1f98f2 | *0x49678AAB11E001eb3cB2cBD9aA96b36DC2461A94 | *
| Polygon | *0x542b9ac4945a3836fd12ad98acbc76a0c8b743f5 | *0x49678AAB11E001eb3cB2cBD9aA96b36DC2461A94 | *
*If a minter blockchain address on the testnet does not have sufficient funds to cover the transaction fee, add some amount to it using a crypto faucet of the blockchain.
*When minting an NFT natively on a blockchain, you are charged a fee for the transaction, and you must sign the transaction with the private key of the blockchain address from which the fee will be deducted.
*Providing the private key in the API is not a secure way of signing transactions, because the private key can be stolen or exposed. Your private keys should never leave your security perimeter. You should use the private keys only for testing a solution you are building on the testnet of a blockchain.
*For signing transactions on the mainnet, we strongly recommend that you use the Tatum Key Management System (KMS) and provide the signature ID instead of the private key in the API. Alternatively, you can use the Tatum JavaScript client.
*You can mint NFTs natively on the following blockchains:
*Depending on what blockchain you use, choose the request body schema to use in the API call.
*MintNftAlgorand schema of the request body.MintNftAlgorandKMS schema of the request body.MintNft schema of the request body.MintNftKMS schema of the request body.MintNftCelo schema of the request body.MintNftKMSCelo schema of the request body.MintNftFlowPK schema of the request body.MintNftFlowMnemonic schema of the request body.MintNftFlowKMS schema of the request body.MintNftSolana schema of the request body.MintNftSolanaKMS schema of the request body.MintNftTron schema of the request body.MintNftKMSTron schema of the request body.100 credits per API call on Flow
* 2 credits per API call on the other blockchains
Transfer an NFT from the smart contract (the contractAddress parameter in the request body) to the specified blockchain address (the to parameter in the request body).
In one API call, you can transfer only one NFT.
*This API is supported for the following blockchains:
*For Ethereum, Celo, and BNB Smart Chain, transferring NFTs invokes the safeTransfer() method.
Transferring NFTs on Algorand
*transferNftAlgoExpress schema of the request body.Transferring NFTs on Solana
*If you want to transfer an NFT that was minted using NFT Express, see the section about minting NFTs on Solana using the pre-built NFT smart contract provided by Tatum for the information about how to set up the parameters in the request body.
*Signing a transaction
*When transferring an NFT, you are charged a fee for the transaction, and you must sign the transaction with the private key of the blockchain address from which the fee will be deducted.
*Providing the private key in the API is not a secure way of signing transactions, because the private key can be stolen or exposed. Your private keys should never leave your security perimeter. You should use the private keys only for testing a solution you are building on the testnet of a blockchain.
*For signing transactions on the mainnet, we strongly recommend that you use the Tatum Key Management System (KMS) and provide the signature ID instead of the private key in the API. Alternatively, you can use the Tatum JavaScript client.
*NOTE: This does not apply to transferring NFTs that were minted on Algorand using NFT Express (see earlier in this section).
* * @param requestBody * @param xTestnetType Type of Ethereum testnet. Defaults to Sepolia. Valid only for ETH invocations for testnet API Key. For mainnet API Key, this value is ignored. * @returns any OK * @throws ApiError */ public static nftTransferErc721( requestBody: (TransferNft | TransferNftCelo | TransferNftTron | TransferNftSolana | TransferNftAlgo | TransferNftAlgoExpress | TransferNftFlowPK | TransferNftFlowMnemonic | TransferNftKMS | TransferNftKMSCelo | TransferNftAlgoKMS | TransferNftSolanaKMS | TransferNftFlowKMS | TransferNftKMSTron), xTestnetType: 'ethereum-sepolia' = 'ethereum-sepolia', ): CancelablePromise<(TransactionHash | SignatureId)> { return __request({ method: 'POST', path: `/v3/nft/transaction`, headers: { 'x-testnet-type': xTestnetType, }, body: requestBody, mediaType: 'application/json', errors: { 400: `Bad Request. Validation failed for the given object in the HTTP Body or Request parameters.`, 401: `Unauthorized. Not valid or inactive subscription key present in the HTTP Header.`, 403: `Forbidden. The request is authenticated, but it is not possible to required perform operation due to logical error or invalid permissions.`, 500: `Internal server error. There was an error on the server during the processing of the request.`, }, }); } /** * Mint multiple NFTs *100 credits per API call on Flow
* 2 credits per API call on the other blockchains
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:
*{
* "to": ["0x80d8bac9a6901698b3749fe336bbd1385c1f98f2"],
* "url": ["ipfs://QmXJJ6UF5WkF4WTJvsdhiA1etGwBLfpva7Vr9AudGMe3pj"],
* "tokenId": ["9876541124516"],
* "contractAddress":"0xcd2ada00c48a27faa5cc67f9a1ed55b89ddf7f77",
* "minter": "0x542b9ac4945a3836fd12ad98acbc76a0c8b743f5",
* "chain": "MATIC"
* }
* The blockchain fee of the performed transaction is paid from the address connected with built-in private key and is debitted in form of credits. The credits are debitted 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 | *
100 credits per API call on Flow
* 2 credits per API call on the other blockchains
Burn one NFT Token. This method destroys any NFT token from smart contract defined in contractAddress.
*This API is supported for the following blockchains:
*Signing a transaction
*When burning an NFT, you are charged a fee for the transaction, and you must sign the transaction with the private key of the blockchain address from which the fee will be deducted.
*Providing the private key in the API is not a secure way of signing transactions, because the private key can be stolen or exposed. Your private keys should never leave your security perimeter. You should use the private keys only for testing a solution you are building on the testnet of a blockchain.
*For signing transactions on the mainnet, we strongly recommend that you use the Tatum Key Management System (KMS) and provide the signature ID instead of the private key in the API. Alternatively, you can use the Tatum JavaScript client.
* * @param requestBody * @param xTestnetType Type of Ethereum testnet. Defaults to Sepolia. Valid only for ETH invocations for testnet API Key. For mainnet API Key, this value is ignored. * @returns any OK * @throws ApiError */ public static nftBurnErc721( requestBody: (BurnNft | BurnNftCelo | BurnNftKMSCelo | BurnNftTron | BurnNftKMSTron | BurnNftKMS | BurnNftFlowPK | BurnNftFlowMnemonic | BurnNftFlowKMS), xTestnetType: 'ethereum-sepolia' = 'ethereum-sepolia', ): CancelablePromise<(TransactionHash | SignatureId)> { return __request({ method: 'POST', path: `/v3/nft/burn`, headers: { 'x-testnet-type': xTestnetType, }, body: requestBody, mediaType: 'application/json', errors: { 400: `Bad Request. Validation failed for the given object in the HTTP Body or Request parameters.`, 401: `Unauthorized. Not valid or inactive subscription key present in the HTTP Header.`, 403: `Forbidden. The request is authenticated, but it is not possible to required perform operation due to logical error or invalid permissions.`, 500: `Internal server error. There was an error on the server during the processing of the request.`, }, }); } /** * Add an NFT minter *2 credits per API call
*Add new minter of NFT Tokens. This method adds minter permission to new minter address.
*This API is supported for the following blockchains:
*Signing a transaction
*When adding an NFT minter, you are charged a fee for the transaction, and you must sign the transaction with the private key of the blockchain address from which the fee will be deducted.
*Providing the private key in the API is not a secure way of signing transactions, because the private key can be stolen or exposed. Your private keys should never leave your security perimeter. You should use the private keys only for testing a solution you are building on the testnet of a blockchain.
*For signing transactions on the mainnet, we strongly recommend that you use the Tatum Key Management System (KMS) and provide the signature ID instead of the private key in the API. Alternatively, you can use the Tatum JavaScript client.
* * @param requestBody * @param xTestnetType Type of Ethereum testnet. Defaults to Sepolia. Valid only for ETH invocations for testnet API Key. For mainnet API Key, this value is ignored. * @returns any OK * @throws ApiError */ public static nftAddMinter( requestBody: (AddNftMinter | AddNftMinterKMS), xTestnetType: 'ethereum-sepolia' = 'ethereum-sepolia', ): CancelablePromise<(TransactionHash | SignatureId)> { return __request({ method: 'POST', path: `/v3/nft/mint/add`, headers: { 'x-testnet-type': xTestnetType, }, body: requestBody, mediaType: 'application/json', errors: { 400: `Bad Request. Validation failed for the given object in the HTTP Body or Request parameters.`, 401: `Unauthorized. Not valid or inactive subscription key present in the HTTP Header.`, 403: `Forbidden. The request is authenticated, but it is not possible to required perform operation due to logical error or invalid permissions.`, 500: `Internal server error. There was an error on the server during the processing of the request.`, }, }); } /** * Verify an NFT in an NFT collection on Solana *2 credits per API call
*Verify an NFT in an NFT collection on Solana. Verifying an NFT sets the Verified parameter to true for the NFT, which means that the NFT is really a part of the collection. To know more about Solana collections and verification, refer to the Solana user documentation.
The collection must be a sized collection that was introduced in Version 1.3 of the Metaplex Token Metadata program. The NFT must have been minted in this collection.
*This API is supported only for Solana.
*Signing a transaction
*When verifying an NFT, you are charged a fee for the transaction, and you must sign the transaction with the private key of the blockchain address from which the fee will be deducted.
*Providing the private key in the API is not a secure way of signing transactions, because the private key can be stolen or exposed. Your private keys should never leave your security perimeter. You should use the private keys only for testing a solution you are building on the testnet of a blockchain.
*For signing transactions on the mainnet, we strongly recommend that you use the Tatum Key Management System (KMS) and provide the signature ID instead of the private key in the API. Alternatively, you can use the Tatum JavaScript client.
* * @param requestBody * @returns any OK * @throws ApiError */ public static nftVerifyInCollection( requestBody: (VerifySolanaNFT | VerifySolanaNFTKMS), ): CancelablePromise<(TransactionHash | SignatureId)> { return __request({ method: 'POST', path: `/v3/nft/verify`, body: requestBody, mediaType: 'application/json', errors: { 400: `Bad Request. Validation failed for the given object in the HTTP Body or Request parameters.`, 401: `Unauthorized. Not valid or inactive subscription key present in the HTTP Header.`, 403: `Forbidden. The request is authenticated, but it is not possible to required perform operation due to logical error or invalid permissions.`, 500: `Internal server error. There was an error on the server during the processing of the request.`, }, }); } /** * Update NFT royalty *2 credits per API call
*Update royalty cashback value for one NFT Token. This method updates the first royalty value of specific author for 1 token. * If royalty value is set to 0, it will disable the royalty system for the token. Only from author's address of the royalty can change it's royalty value, not the owner of the token.
*This API is supported for the following blockchains:
*Signing a transaction
*When updating NFT royalty, you are charged a fee for the transaction, and you must sign the transaction with the private key of the blockchain address from which the fee will be deducted.
*Providing the private key in the API is not a secure way of signing transactions, because the private key can be stolen or exposed. Your private keys should never leave your security perimeter. You should use the private keys only for testing a solution you are building on the testnet of a blockchain.
*For signing transactions on the mainnet, we strongly recommend that you use the Tatum Key Management System (KMS) and provide the signature ID instead of the private key in the API. Alternatively, you can use the Tatum JavaScript client.
* * @param requestBody * @param xTestnetType Type of Ethereum testnet. Defaults to Sepolia. Valid only for ETH invocations for testnet API Key. For mainnet API Key, this value is ignored. * @returns any OK * @throws ApiError */ public static nftUpdateCashbackErc721( requestBody: (UpdateCashbackValueForAuthorNft | UpdateCashbackValueForAuthorNftCelo | UpdateCashbackValueForAuthorNftTron | UpdateCashbackValueForAuthorNftKMS | UpdateCashbackValueForAuthorNftKMSCelo | UpdateCashbackValueForAuthorNftKMSTron), xTestnetType: 'ethereum-sepolia' = 'ethereum-sepolia', ): CancelablePromise<(TransactionHash | SignatureId)> { return __request({ method: 'PUT', path: `/v3/nft/royalty`, headers: { 'x-testnet-type': xTestnetType, }, body: requestBody, mediaType: 'application/json', errors: { 400: `Bad Request. Validation failed for the given object in the HTTP Body or Request parameters.`, 401: `Unauthorized. Not valid or inactive subscription key present in the HTTP Header.`, 403: `Forbidden. The request is authenticated, but it is not possible to required perform operation due to logical error or invalid permissions.`, 500: `Internal server error. There was an error on the server during the processing of the request.`, }, }); } /** * Get NFT transactions on a blockchain address *1 credit per API call
*Get incoming and outgoing NFT transactions on a blockchain address.
*This API is supported for the following blockchains:
*1 credit per API call
Get NFT transactions by token. This includes incoming and outgoing transactions for the token.
This API is supported for the following blockchains:
1 credit per API call
*Get NFT transaction by transaction hash.
*This API is supported for the following blockchains:
*1 credit per API call + 5 credits for each owned NFT
*Get all NFTs that a blockchain address holds. The NFTs are returned grouped by the smart contracts they were minted on.
*This API is supported for the following blockchains:
*On Solana and Algorand, if a blockchain address holds fewer than 50 NFTs, the API also returns each NFT's metadata. If the metadata is not returned, you can obtain it using the API for getting NFT metadata.
* * @param chain Blockchain to work with * @param address The blockchain address that you want to get the token balance of * @returns any OK * @throws ApiError */ public static nftGetTokensByAddressErc721( chain: 'ALGO' | 'CELO' | 'ETH' | 'MATIC' | 'SOL', address: string, ): CancelablePromise1 credit per API call + 5 credits for each listed NFT
*Get all minted NFTs in the collection. Returns all NFTs this contract minted.
*This API is supported for the following blockchains:
*1 credit per API call
*Get the NFTs minted on a specific smart contract (the contractAddress path parameter in the request endpoint URL) that a blockchain address holds.
NOTE: This API works only for the NFT smart contracts deployed using the Tatum smart contract API.
*This API is supported for the following blockchains:
*1 credit per API call
*Get NFT token provenance data, valid only for provenance contract.
*This API is supported for the following blockchains:
*1 credit per API call
*Get NFT token metadata.
*This API is supported for the following blockchains:
*1 credit per API call
*Get NFT token royalty.
*This API is supported for the following blockchains:
*This endpoint is deprecated. Do not use it.
* Instead, use this API.
1 credit per API call
*Get NFT contract address from deploy transaction.
*This API is supported for the following blockchains:
*