TRC-721 NFT Standard

TRC-721 is a standard interface for issuing non-fungible tokens (NFT) on the TRON network. Tokens created on the TRC-721 standard can represent any digital type of tangible assets in the real world. TRC-721 is fully compatible with ERC-721.

Blockchain API

Work with TRC-721 tokens via the CryptoAPIs API

Read TRC-721 token transfers, balances, and metadata across the chains CryptoAPIs supports — through one unified REST API, with no node to run.

Token transfers

List full TRC-721 token transfer history for any token contract or address, with pagination and real-time updates.

Token balances

Read current TRC-721 token holdings for any address in a single call.

Contract metadata

Get token contract details — symbol, name, decimals, and total supply — for any supported token.

Token standard

More opportunities for developers

The TRC-721 standard has as important role for the TRON blockchain as TRC-20. It provides many opportunities for developers to create new applications based on the blockchain, and to track and transfer NFTs on TRON.

Token standards

Other token standards the API reads

FAQ

Frequently Asked Questions

Which blockchain does TRC-721 run on?

TRC-721 settles on Tron. It keeps ERC-721's per-token-id semantics while settling on Tron, so the same NFT logic applies but the fee model and address format do not.

What kind of token standard is TRC-721?

It is a non-fungible interface, Tron's counterpart to ERC-721.

Can I test TRC-721 without spending real funds?

Yes — the same endpoints serve Tron's Nile testnet, so you can build and verify an integration end to end before you touch mainnet.

How do I read TRC-721 balances and transfers?

Use Address Latest for current state and recent activity — it needs no setup and answers for roughly the last 14 days. For a full history, Address History requires the address to be synced first, which then bills per address per day for as long as it stays synced.

What does reading TRC-721 data cost?

It depends on the endpoint family rather than on TRC-721 itself: single-record calls are charged per request, while list endpoints are charged per page returned, and a synced address adds a daily monitoring charge. The pricing calculator has the current per-chain figures.

Build with TRC-721 tokens on CryptoAPIs

Now that you know what TRC-721 is, integrate it: read TRC-721 token transfers, balances, and contract metadata across supported chains through one REST API.