SFTs (semi-fungible tokens) follow the ERC-1155 standard. Each token is a replica of a predefined template. Each collection (smart contract) can contain multiple templates, which can contain many tokens.
This API only supports EVM chains self-serve. Contact us if you need support for another chain.
Once you log in to the console, the next step is to create an .
Click the "Integrate" tab and click on the "API Keys" option on top.
Within the “Server-side keys” section, click the “Create new key” button in the top right.
Then, check the scopes nfts.create, nfts.read, and collections.create under the “Minting API”
category and create your key. Save this key for the next step.
The mint has started processing. However, blockchains can take a few seconds (or,
at times of extreme network congestion, even minutes) to confirm the operation.
Before showing the user a success screen, the next step is checking the
status of the mint.
To do this, grab the actionId received at the end of step 5 and use it
alongside your API key in one of the snippets below.
Pay attention to the “status” field. Once it says “success”:
Congratulations. You have minted your first SFT 🥷 🎉
For scalable production applications, consider using webhooks to
determine when your SFT has been minted, instead of periodically polling for its status via the API.
If the SFTs were delivered to a wallet address, the user will be able to see them there directly, connecting to testnet if needed, or on the testnet blockchain explorer.
And voilá, there’s your SFT! Now think of all the cool things you can build
with this, at scale :)
Then, create a production key on the API Keys page with the
same API scopes.
Modify all code snippets with const env = "www", so they use the production APIs. You may also need to change the
chain variable to match your production blockchain.