---
title: "Verify an NFT in an NFT collection on Solana"
method: POST
path: "/v3/nft/verify"
tags: ["NFT (ERC-721 or compatible)"]
---

# Verify an NFT in an NFT collection on Solana

`POST /v3/nft/verify`

## Request

- Base URL: `https://api.tatum.io`
- URL: `https://api.tatum.io/v3/nft/verify`
- Auth: API key in header `x-api-key`

/v3/nft/verify

**2 credits per API call**

Verify an NFT in an NFT collection on Solana. Verifying an NFT sets the `Verified` parameter to `true` for the NFT, which means that the NFT is really a part of the collection. To know more about Solana collections and verification, refer to the [Solana user documentation](https://docs.metaplex.com/programs/token-metadata/certified-collections).

The collection must be a sized collection that was introduced in [Version 1.3](https://docs.metaplex.com/programs/token-metadata/changelog/v1.3) of the Metaplex Token Metadata program. The NFT must have been [minted in this collection](#operation/NftMintErc721).

This API is supported only for Solana.

**Signing a transaction**  
When verifying an NFT, you are charged a fee for the transaction, and you must sign the transaction with the private key of the blockchain address from which the fee will be deducted.

Providing the private key in the API is not a secure way of signing transactions, because the private key can be stolen or exposed. Your private keys should never leave your security perimeter. You should use the private keys only for testing a solution you are building on the **testnet** of a blockchain.

For signing transactions on the **mainnet**, we strongly recommend that you use the Tatum [Key Management System (KMS)](https://github.com/tatumio/tatum-kms) and provide the signature ID instead of the private key in the API. Alternatively, you can use the [Tatum JavaScript client](https://github.com/tatumio/tatum-js/tree/v2).

## Request body

- union
  - VerifySolanaNFT
    - `chain` 'SOL', required: The blockchain to work with
    - `nftAddress` string, required: The blockchain address of the NFT to verify
    - `collectionAddress` string, required: The blockchain address of the NFT collection where the NFT should be verified in. The collection must be a sized collection that was introduced in <a href="https://docs.metaplex.com/programs/token-metadata/changelog/v1.3" target="_blank">Version 1.3</a> of the Metaplex Token Metadata program.
    - `from` string, required: The blockchain address of the collection verifier on behalf of whom the transaction will be originated. The transaction fee will be paid from this address.
    - `fromPrivateKey` string, required: The private key of the collection verifier's address
    - `feePayer` string: Address on the Solana blockchain, from which the fee will be paid for transaction. Defaults to from.
    - `feePayerPrivateKey` string: Private key of the fee payer address.
  - VerifySolanaNFTKMS
    - `chain` 'SOL', required: The blockchain to work with
    - `nftAddress` string, required: The blockchain address of the NFT to verify
    - `collectionAddress` string, required: The blockchain address of the NFT collection where the NFT should be verified in. The collection must be a sized collection that was introduced in <a href="https://docs.metaplex.com/programs/token-metadata/changelog/v1.3" target="_blank">Version 1.3</a> of the Metaplex Token Metadata program.
    - `from` string, required: The blockchain address of the collection verifier on behalf of whom the transaction will be originated. The transaction fee will be paid from this address.
    - `signatureId` string, uuid, required: Identifier of the private key associated in signing application. Private key, or signature Id must be present.
    - `feePayer` string: Blockchain address to pay the fee for the transaction from
    - `feePayerSignatureId` string, uuid: Identifier of the private key used for paying the gas costs in signing application. Defaults to the signatureId.

## Response `200`

OK

- union
  - TransactionHash
    - `txId` string, required: The hash (ID) of the transaction
  - SignatureId
    - `signatureId` string, uuid, required: The internal Tatum ID of the prepared transaction for Key Management Sysytem (KMS) to sign<br/>This is different from the <code>signatureId</code> parameter that you provided in the request body. The <code>signatureId</code> parameter in the request body specifies the signature ID associated with the private key in KMS.

## Other responses

- `400`: Bad Request
- `401`: Unauthorized. Not valid or inactive subscription key present in the HTTP Header.
- `403`: Forbidden. The request is authenticated, but it is not possible to perform the operation due to logical error or invalid permissions.
- `500`: Internal server error. There was an error on the server during the processing of the request.

---

[API](https://skmtc.dev/tatum/apis/smart-contracts.md) - [All operations](https://skmtc.dev/tatum/apis/smart-contracts/llms.txt) - [OpenAPI document](https://skmtc.dev/tatum/apis/smart-contracts/revisions/c0146043bb37?raw)