---
title: "Retrieve an NFT"
method: GET
path: "/v2/nfts/{mintAddress}"
tags: ["NFTs"]
---

# Retrieve an NFT

`GET /v2/nfts/{mintAddress}`

## Path parameters

- `mintAddress` string, required — Base-58 encoded string representing an on-chain address

## Response `200`

Successful response

- object
  - `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
  - `id` number, required — Unique ID for an NFT in a Project
  - `projectId` number — The ID of the Project the NFT is part of
  - `transferable` boolean — Whether or not the NFT can be transferred based on the Project its a part of
  - `compressed` boolean — Whether or not the NFTs in the Project are compressed
  - `mintAddress` string, required — Base-58 encoded string representing an on-chain address
  - `ownerAddress` string — Wallet address for the NFT's owner
  - `claimerAddress` string — Wallet address allowed to claim the NFT
  - `status` string, required

## Other responses

- `404` — Not Found

---

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