For the complete documentation index, see llms.txt. This page is also available as Markdown.

nft_info

Returns information about the NFT being queried: its current owner, issuer, taxon, flags, transfer fee, URI and whether it has been burned.

This method will use 20 Compute Units.


Reference: Here

Parameters

  • nft_id (string, required) A unique identifier for the non-fungible token (NFT).

  • ledger_hash (string, optional) The unique hash of the ledger version to use.

  • ledger_index (string or unsigned integer, optional) The ledger index of the ledger to use, or a shortcut string. Do not use closed or current; those forward the request to rippled, which does not support this method.

Returns

  • nft_id (string) A unique identifier for the NFT.

  • ledger_index (integer) The ledger index of the most recent ledger version where the state of this NFT was modified (minted, traded or burned).

  • owner (string) The account that owns this NFT at this ledger index.

  • is_burned (boolean) true if the NFT is burned at this ledger.

  • flags (integer) The flag set of this NFT.

  • transfer_fee (integer) The transfer fee of this NFT, in units of 1/100,000.

  • issuer (string) The account that issued this NFT.

  • nft_taxon (integer) The NFT's taxon.

  • nft_serial (integer) The NFT's sequence number.

  • uri (string) The NFT's URI in hexadecimal, or an empty string if the NFT does not have a URI.

  • validated (boolean) If true, the information comes from a validated ledger version.

Over WebSocket, send {"id":1,"command":"nft_info","nft_id":"0008170207397A8AA414511E6E0649C9980E185E1C19D74010CEAF0005E46EE3","ledger_index":"validated"} to wss://mainnet.xrpl.validationcloud.io/v1/<YOUR_API_KEY_HERE>.

This method is served by Clio, our full-history XRPL server, and is not available from rippled.

Last updated

Was this helpful?