GET
/
2022-06-09
/
collections
/
{collectionId}
/
nfts
/
{id}
Mint Status
curl --request GET \
  --url https://staging.crossmint.com/api/2022-06-09/collections/{collectionId}/nfts/{id} \
  --header 'X-API-KEY: <api-key>'
  {
    "id": "<string>",
    "metadata": {
      "name": "<string>",
      "image": "<string>",
      "description": "<string>"
    },
    "onChain": {
      "status": "success",
      "tokenId": "<string>",
      "owner": "<string>",
      "txId": "<string>",
      "contractAddress": "<string>",
      "chain": "polygon"
    },
    "action": "https://staging.crossmint.com/api/2022-06-09/actions/<actionId>"
  }

  {
    "id": "<string>",
    "metadata": {
      "name": "<string>",
      "image": "<string>",
      "description": "<string>"
    },
    "onChain": {
      "status": "success",
      "tokenId": "<string>",
      "owner": "<string>",
      "txId": "<string>",
      "contractAddress": "<string>",
      "chain": "polygon"
    },
    "action": "https://staging.crossmint.com/api/2022-06-09/actions/<actionId>"
  }

Authorizations

​
X-API-KEY
string
header
required

Obtained in the Crossmint developer console

Path Parameters

​
collectionId
string
required

This is the identifier for the collection related to the request. Every project has default collections: default-solana and default-polygon.

The create-collection API will result in collections with UUID formatted collectionId. Example: 9c82ef99-617f-497d-9abb-fd355291681b

The create-collection-idempotent API allows you to specify an arbitrary identifier during the intitial request. Example: your-custom-identifer

​
id
string
required

Unique ID of the minted NFT returned in the mint response

Response

200
application/json

Success.

The response is of type object.