NFT | Creation & Management
Last updated
Was this helpful?
Last updated
Was this helpful?
Create and mint NFTs via the FA2 (Financial Application 2) unified token standard on Tezos, offering the following token types:
fungible (equals on Ethereum)
non-fungible (equals on Ethereum)
non-transferable (equals on Ethereum)
multi-asset contracts (equals on Ethereum)
The FA2 standard has multiple implementations. We support the following:
Single
With this implementation, you can only have one collection. It is like the ERC-721 style. Only owner minter can mint new NFTs.
Multiple
With this implementation, you can have multiple collections. In each collection, you can define the number of copies of each NFT. It is somehow like the ERC-1155 style.
We offer a set of default FA2 based smart contract templates, providing the main functionality needed for NFT projects.
|
Path parameters:
chain: [string] chain to work with. Either TEZOS or GHOSTNET.
owner: [string] the owner(Admin) of the smart contract.
type: [string] the FA2 smart contract implementation. Either SINGLE or MULTIPLE. For more explanation, you can click .
Example:
The FA2 smart contract implementation allows minting NFTs from different accounts. The owner of the smart contract is allowed to add new minters.
With this API, you can mint a new NFT. It have multiple options to manages NFT minting. You can generate NFT URI metadata by yourself or let the NFT KIT generate it.
Path parameters:
chain: [string] chain to work with. Either TEZOS or GHOSTNET.
contract: [string] smart contract address
Body parameters:
metadataUri: [string] metadata URI of the new token.If you want to generate metadata URI using NFT KIT, set the "metadataUri "value as an empty string.
tokenId: [string] the account address who will receive the NFT
amount: [string] the account address who will receive the NFT
recipientAddress: [string] the account address who will receive the NFT
description: [string] a description of the token
name: [string] the name of this specific token
image: [string] this is the URL to the image of the item. Can be just about any type of image and can be IPFS URLs or paths.
image_data: [string] Raw SVG image data, if you want to generate images on the fly (not recommended). Only use this if you're not including the image parameter.
external_url: [string] This is the URL that will appear below the asset's image on OpenSea and will allow users to leave OpenSea and view the item on your site.
attributes: [string] To give your items a little more pizazz, we also allow you to add custom "attributes" to your metadata that will show up underneath each of your assets.
trait_type: [string] the name of the trait
value: [string] the value of the trait
Example:
You can get the NFT metadata based on the NFT smart contract address and the NFT token ID.
You get the NFTs list of an account on the specified network.
This API allows fetching contract metadata.
|
|
metadata: NFT KIT will use values inside metadata to generate metadata URI of the new token. It confirms the structure defined by ERC721 and ERC1155 standards. For more details about .
|
|
|