---
title: "Update an NFT"
method: PUT
path: "/v2/projects/{projectId}/nfts/{nftId}"
tags: ["Projects"]
---

# Update an NFT

`PUT /v2/projects/{projectId}/nfts/{nftId}`

This endpoint allows you to perform an update on an NFT.

## Path parameters

- `projectId` integer, required
- `nftId` integer, required

## Request body

- Metadata
  - `name` string, required — Name stored as on-chain metadata
  - `symbol` string — Symbol stored as on-chain metadata
  - `description` string — Description stored in the metadata
  - `image` string, required — Image for your NFT. When creating an NFT, this can be a base64 encoded string or a URL pointing to an image.
  - `animationUrl` string — URL pointing to the asset's animation.
  - `externalUrl` string — URL pointing to an external URL defining the asset
  - `attributes` object — Key-value pairs of your NFT attributes

## Response `200`

Returns an Updated NFT

- UpdateAssetResponse
  - `transactionId` string, required — Transaction ID that identifies the Transaction generated by an API request
  - `nftId` number, required — Unique ID for an NFT in a Project
  - `projectId` number — The ID of the Project the NFT is part of
  - `mintAddress` string, required — Base-58 encoded string representing an on-chain address

## Other responses

- `401` — Unauthorized
- `403` — Forbidden
- `404` — Not Found

---

[API](https://skmtc.net/underdogprotocol/apis/underdog-protocol-api.md) · [All operations](https://skmtc.net/underdogprotocol/apis/underdog-protocol-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/underdogprotocol/underdog-protocol-api/versions/714574b82cc5/schema)