> For the complete documentation index, see [llms.txt](https://docs.claimr.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.claimr.io/tasks/web3-tasks/mint-an-nft-1155.md).
# Mint an NFT (1155)
ERC-1155 is a token standard that allows for both fungible and non-fungible tokens to be created within the same contract. This means it can be used to represent unique NFTs (like ERC-721) as well as semi-fungible tokens or multiple copies of the same NFT.
### Before you start
Make sure you have:
* A quest created within your campaign
* The ERC-1155 NFT collection contract address
* The specific Token ID you want users to mint
* Knowledge of which blockchain network the NFT is deployed on
* Mint fee amount (if applicable)
### Create the task
Follow the steps in Web3 tasks to navigate to the task creation screen, select **Web3** from the Groups section, and choose **Mint an NFT (EVM 1155)**.
### Task settings
**Completion points**: Set the number of points awarded when the user completes the task.
**Points multiplier (%)**: Add a percentage-based bonus to the total reward. For example, a 10% multiplier increases the final reward by 10%.
**Recurrence**: Control how often users can complete the task:
* **Once** – can only be completed one time per user
* **8h** – available once every eight hours
* **Daily** – available once every 24 hours
* **Weekly** – available once every 7 days
* **Multiple** – stays open and can be completed as many times as needed, one after another, without any waiting time
**Network**: Select the blockchain network on which the NFT will be minted.
* Click the first dropdown to choose a network (e.g., Ethereum)
* Click the second dropdown to select Mainnet or Testnet
**Contract Address**: Enter the contract address of the ERC-1155 NFT collection or project.
* This is the specific contract where the ERC-1155 tokens are deployed
* Example placeholder: "eg. 0x0d5cc359f67076b5804e2b32aad75bd8631cd12b"
**Has server signature support (optional)**: Toggle this on if your NFT minting process requires server-side signature support. This is an advanced security feature that protects your NFT mint from unauthorized minting
To utilize this feature, you will need a special contract template—request this from the Claimr support team. See the explanation in the [ERC-721 section](/tasks/web3-tasks/mint-an-nft-721.md) for why server-side signatures are important
**Token Id**: Specify the ID of the token within the ERC-1155 contract that you want users to mint. Each ID represents a different token type within the same contract
**Amount**: Specify the number of tokens with the specified ID that users need to mint to complete the task. This allows users to mint multiple copies of the same token
**Mint Fee (optional)**: If there's a fee associated with minting the NFT, specify the amount here.
### **Pro tips**
* Provide clear and concise instructions on how to mint the ERC-1155 NFT, including any necessary steps like connecting a wallet, approving transactions, or paying minting fees
* Specify the NFT collection or project name, the token ID, the benefits of owning the NFT, and any relevant links (e.g., to the minting website or marketplace) in the task description
* Consider displaying images or previews of the NFTs within the task description to make it more engaging
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.claimr.io/tasks/web3-tasks/mint-an-nft-1155.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.