GET
/
insights
/
v1
/
nfts
/
{contract_address}
/
{token_id}
Get NFT by token ID
curl --request GET \
  --url https://data-api.b3.fun/insights/v1/nfts/{contract_address}/{token_id}
{
  "data": [
    {
      "chain_id": 123,
      "contract_address": "vitalik.eth",
      "token_id": "<string>",
      "token_type": "<string>",
      "balance": "<string>",
      "owner_addresses": [
        "<string>"
      ],
      "name": "<string>",
      "description": "<string>",
      "image_url": "<string>",
      "video_url": "<string>",
      "animation_url": "<string>",
      "background_color": "<string>",
      "external_url": "<string>",
      "status": "<string>",
      "metadata_url": "<string>",
      "extra_metadata": {
        "attributes": [
          {
            "trait_type": "<string>",
            "value": "<string>",
            "display_type": "<string>"
          }
        ],
        "properties": {}
      },
      "collection": {
        "name": "<string>",
        "description": "<string>",
        "image_url": "<string>",
        "banner_image_url": "<string>",
        "featured_image_url": "<string>",
        "external_link": "<string>"
      },
      "contract": {
        "chain_id": 1,
        "address": "vitalik.eth",
        "name": "<string>",
        "symbol": "<string>",
        "type": "erc721"
      }
    }
  ]
}

Path Parameters

​
contract_address
string
required
Example:

"vitalik.eth"

​
token_id
string
required

Query Parameters

​
chain
number[]
deprecated

Use chain_id instead

Example:
[20, 56, 1]
​
chain_id
number[]

The chain ID(s) to request the data for. You can specify multiple chain IDs, up to a maximum of 55. Use repeated query parameters, e.g., ?chain_id=20&chain_id=56. Optional, because a single chain can as well be specified as a subdomain

Example:
[20, 56, 1]
​
include_owners
enum<string>
default:false

Whether to include owner addresses in the NFT metadata (only if metadata is requested)

Available options:
true,
false
Example:

"false"

​
resolve_metadata_links
enum<string>
default:true

Whether to resolve metadata IPFS or Arweave links

Available options:
true,
false
Example:

"false"

Response

200
application/json

Success

The response is of type object.