---
title: "Edit NFT"
method: PATCH
path: "/2022-06-09/collections/{collectionId}/nfts/{id}"
tags: ["NFTs"]
---

# Edit NFT

`PATCH /2022-06-09/collections/{collectionId}/nfts/{id}`

Edit a minted NFT's metadata on IPFS. 

If you are using a custom baseURI, invoking this will overwrite the specific tokenURI for the edited token.

**API scope required**: `nfts.update`

## Path parameters

- `collectionId` string, required
- `id` string, required

## Request body

- object
  - `metadata` union, required — Optional if [baseURI](/api-reference/minting/collection/set-base-uri) is set.
    - NFTMetadata
      - `name` string, required — The name of your NFT (Max length: 32)
      - `image` string, required — Direct link to your NFT image
      - `description` string, required — A brief description of the NFT (Max length: 64)
      - `animation_url` string — **EVM only** [See more info here](/minting/nfts/integrate/define-metadata)
      - `attributes` object[] — Add attributes to your NFT
        - `display_type` 'boost_number' | 'boost_percentage' | 'number' — Display name of your attribute
        - `trait_type` string, required — The name of the trait
        - `value` string, required — The value of the trait
    - string — Enter a URL to a JSON file containing the metadata contents
    - NFTMetadataSolana
      - `name` string, required — The name of your NFT (Max length: 32)
      - `image` string, required — Direct link to your NFT image
      - `description` string, required — A brief description of the NFT (Max length: 64)
      - `symbol` string — **Solana only** A shorthand identifier for the token (Max length: 10)
      - `attributes` object[] — Add attributes to your NFT
        - `display_type` 'boost_number' | 'boost_percentage' | 'number' — Display name of your attribute
        - `trait_type` string, required — The name of the trait
        - `value` string, required — The value of the trait
    - object — Enter a URL to a JSON file containing the metadata contents
      - `uri` string, required — Enter a URL to a JSON file containing the metadata contents
      - `name` string, required — The name of your NFT (Max length: 32)
  - `reuploadLinkedFiles` boolean — Any URLs in the metadata object will be resolved and reuploaded to IPFS [Default: true]

## Response `200`

The NFT metadata update action has been successfully been created.

- EditNFTResponse
  - `actionId` string
  - `action` string
  - `status` string
  - `data` object
    - `txId` string — The onchain transaction ID related to the request. This is only present when `status` is `succeeded`
    - `chain` string
    - `collection` object
      - `id` string
      - `contractAddress` string
    - `token` object
      - `id` string
      - `owner` object
        - `walletAddress` string
      - `tokenId` string
    - `changes` string[]
  - `startedAt` string, date-time
  - `completedAt` string, date-time — The time this operation completed in UTC. This is only present when `status` is `succeeded`
  - `resource` string

## Other responses

- `400` — Invalid arguments, please make sure you're following the api specification.
- `403` — Forbidden error, please ensure the credentials are correct.
- `404` — Not found error.
- `503` — Please try again in a few minutes. If the issue still persists, contact Crossmint support.

---

[API](https://skmtc.net/crossmint/apis/onramp.md) · [All operations](https://skmtc.net/crossmint/apis/onramp/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/crossmint/onramp/revisions/e2143d192130/schema)