PUT
/
api
/
v1
/
nft
/
tokenMetadata
curl 'https://groupos.xyz/api/v1/nft/tokenMetadata' \
--request PUT \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer <token>' \
--data-raw '{
  "chainId": 5,
  "contractAddress": "0x67F4732266C7300cca593C814d46bee72e40659F",
  "tokenId": "10",
  "metadata": {
    "name": "Zed Run",
    "description": "Horses run free in the metaverse.",
    "mediaUrl": "https://hosted.station.express/abc123"
  }
}'

{
  "success": true
}

​
How token metadata works

Both ERC-721 and ERC-1155 NFTs can have individual tokens’ metadata updated. This enables differentiation between NFTs of the same collection and dynamic or evolving use cases.

When edits are made to the NFT’s metadata, updates are propagated automatically to Opensea and other platforms.

​
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 edit.

tokenId
string
required

The individual token ID edit.

metadata
object
required

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

​
Response

success
boolean

Indicates whether the call was successful.

Update Collection MetadataQuery Metadata