This page lists the transactions and requests associated with NFTs as a handy reference.
- NFToken data type - The NFT object stored on the ledger.
- Ledger Objects
- NFTokenOffer object - An offer to buy or sell an NFT.
- NFTokenPage object - An NFT page holds a maximum of 32 NFT objects. In practice, each NFT page typically holds 16-24 NFTs.
NFTokenMint - Create an NFT.
NFTokenCreateOffer - Create an offer to buy or sell an NFT.
NFTokenCancelOffer - Cancel an offer to buy or sell an NFT.
NFTokenAcceptOffer - Accept an offer to buy or sell an NFT.
NFTokenBurn - Permanently destroy an NFT.
- account_nfts method - Get a list of non-fungible tokens owned by an account.
- nft_buy_offers method - Get a list of buy offers for a specified NFToken object.
- nft_sell_offers method - Get a list of sell offers for a specified NFToken object.
- subscribe method - Listen for updates about a particular subject. For example, a marketplace can publish real-time updates on the status of NFTs listed on their platform.
- unsubscribe method - Stop listening for updates about an NFT.
Clio servers enhance overall network performance by handling requests for information based on cached information, freeing up validators on the XRP Ledger to focus on processing transactions. In addition to all of the common XRP Ledger request types, the Clio server handles additional request types that provide more detailed responses.
Clio-specific NFT requests
- nft_info - Get current status information about the specified NFT.
- nft_history - Get past transaction metadata for the specified NFT.
You can access a public Clio server by sending a request to its URL and Clio port (typically 51233). Public Clio API servers come with no SLAs nor any responsibility to be fixed on priority. If your business use case requires continual monitoring and information requests, consider setting up your own Clio server instance. See install-clio-on-ubuntu.