NFT Metadata
Update an NFT Collection's Metadata
NFT Metadata
Update an NFT Collection's Metadata
PUT
/
api
/
v1
/
nft
/
collectionMetadata
Authorization
Body
curl --location --request PUT 'https://groupos.xyz/api/v1/nft/collectionMetadata' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer <token>' \
--data-raw '{
"chainId": 5,
"contractAddress": "0x67F4732266C7300cca593C814d46bee72e40659F",
"metadata": {
"description": "Horses run free in the metaverse.",
"mediaUrl": "https://hosted.app/abc123"
}
}'
{
"success": true,
}
How collection metadata works
For NFT collections that have one standard set of metadata (name, image, etc.) or support evolving metadata schemes, a single set of metadata can be defined at the collection-level to provide this default. Individual metadata can be updated individually as well, which will override the defaults set here.
When edits are made to the collection’s default metadata, updates are propagated automatically to Opensea and other platforms.
Body
chainId
number
requiredThe id of the chain supporting the NFT. This cannot be changed after creation.
contractAddress
string
requiredThe NFT smart contract address to edit.
metadata
object
requiredDefault metadata to apply to every NFT in the collection, which can be overriden with token-specific metadata.
Response
success
boolean
Indicates whether the call was successful.
curl --location --request PUT 'https://groupos.xyz/api/v1/nft/collectionMetadata' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer <token>' \
--data-raw '{
"chainId": 5,
"contractAddress": "0x67F4732266C7300cca593C814d46bee72e40659F",
"metadata": {
"description": "Horses run free in the metaverse.",
"mediaUrl": "https://hosted.app/abc123"
}
}'
{
"success": true,
}