POST
/
api
/
v1
/
erc721
/
mint
curl --location --request POST 'https://groupos.xyz/api/v1/erc721/mint' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer <token>' \
--data-raw '{
    "chainId": 5,
    "contractAddress": "0x67F4732266C7300cca593C814d46bee72e40659F",
    "recipientAddress": "0xc517c83f417b73dA98647dad0FCB80af9f3b9531"
}'

{
  "success": true,
  "transactionHash": "0x58c789b7a59312ec0a659e165700db54af896d3e8b46e4aeecb33b32b88157c9",
  "transactionUrl": "https://goerli.etherscan.io/tx/0xef737091d8c3451b42659688abd86b51516a6b43ee7dbdbda53c9005d86167db"
}

​
How to mint ERC-721 NFTs

Once you have a ERC-721 NFT smart contract, you can mint any number of tokens to any address. Each NFT has a unique tokenId which is an auto-incrementing number like a typical numeric identifier in a database. You can also optionally provide metadata specific to this newly minted NFT that will override any defaults set in the previous step.

​
Body

chainId
number
required

The id of the chain supporting the NFT. This cannot be changed after creation.

contractAddress
string
required

The NFT smart contract address to mint with.

recipientAddress
string
required

The address to mint an NFT to.

metadata
object

Metadata to associate with this NFT, which overrides any defaults set at the collection-level.

​
Response

success
boolean

Indicates whether the call was successful.

transactionHash
string

Transaction hash for the newly created token.

transactionUrl
string

Wraps transactionHash with the appropriate network-specific URL for convenience.

Query OwnersPermit NFTs