WAX Get Assets icon

WAX Get Assets

Get NFTs for an account

WAX Get Assets

AI-generated

Overview

This node retrieves NFTs (non-fungible tokens) for a specified WAX blockchain account. It is useful for users who want to fetch detailed asset information such as asset IDs, template IDs, collection names, and schema names associated with an account on the WAX blockchain. Common scenarios include NFT portfolio tracking, asset management, and integration with NFT marketplaces or analytics platforms.

Use Case Examples

  1. Fetch all NFTs owned by a WAX account to display in a user dashboard.
  2. Filter NFTs by specific template IDs, collections, or schemas for targeted asset analysis.
  3. Retrieve NFT data for use in automated workflows involving blockchain asset verification or transfer.

Properties

Name Meaning
Account Name The WAX blockchain account name to retrieve NFTs for.
Template ID (Optional) Comma-separated list of template IDs to filter the NFTs by.
Collection (Optional) Comma-separated list of collections to filter the NFTs by.
Schema (Optional) Comma-separated list of schemas to filter the NFTs by.
Code The smart contract code on the WAX blockchain, defaulting to 'atomicassets'.
API Endpoint The WAX blockchain API endpoint URL to query, defaulting to 'https://wax.greymass.com'.

Output

JSON

  • account - The WAX account name for which NFTs were retrieved.
  • assets - An array of NFT assets matching the filters, each containing asset_id, template_id, collection_name, and schema_name.

Dependencies

  • Requires connection to the WAX blockchain API endpoint, which may require network access.

Troubleshooting

  • Pagination errors if the API returns inconsistent pagination keys, resulting in a 'pagination did not advance' error. To resolve, verify the API endpoint and account parameters.
  • Empty or missing 'rows' property in the API response may cause errors; ensure the account exists and the endpoint is correct.
  • Exceeding maximum pagination iterations throws an error; consider limiting the number of assets or refining filters to reduce data volume.

Discussion