Start building with Hedera NFT data

An account ID identifies an account. A token ID identifies a collection. A serial identifies one NFT inside that collection. They must be used with the correct network.

Do not treat a collection name or image URL as the NFT's identity. Store the network, token ID and serial together in your application.

Start with mirror nodes explained, then look up an NFT. These are read-only tasks that do not require a private key or wallet connection.

Once one lookup works, list an account's NFTs. That introduces pagination, response validation and the limits of a live data view.

Use the JavaScript SDK introduction to learn the transaction building blocks. Continue with one NFT on testnet before planning any mainnet integration.

Keep signing credentials out of browser bundles, examples and source control. A production wallet connection needs its own consent and security design; a beginner server-side sample is not that design.

A mirror node records network information. It does not automatically know the meaning of every marketplace listing or application-specific event.

Use the SentX API for the market data documented there. Keep identifiers consistent when connecting its results to ledger data, and keep a recorded sale distinct from an arbitrary NFT transfer.

Networks and data providers can time out. Keep the original transaction identifier and resolve that operation before creating a replacement. Read the transaction-status guide before implementing retries.

Start small: one network, one known NFT and one question answered correctly.