MultiversX icon

MultiversX

MultiversX blockchain operations: Execute smart contracts, check balances, transfer tokens, query accounts, get transactions, and access network data. Can inspect ABI functions and contract details. ALWAYS validate ABI functions before execution. Automatically provides contract context to AI including address and available functions.

API Query

AI-generated

Overview

This node enables querying the MultiversX blockchain API to retrieve various types of blockchain data without interacting with smart contracts directly. It supports fetching information about accounts, blocks, transactions, network status and configuration, tokens, NFTs, validators, and network economics.

Common scenarios where this node is beneficial include:

  • Retrieving account balances, token holdings, or transaction history for a given address.
  • Fetching details about specific transactions or their statuses.
  • Getting the latest block data or querying blocks by hash.
  • Accessing network-wide statistics, configuration, or economic parameters.
  • Listing NFT collections or details about specific NFTs.
  • Querying token metadata or listing all tokens.
  • Obtaining validator node information and staking details.

Practical examples:

  • A user wants to monitor an account’s EGLD balance and recent transactions.
  • An application needs to display the current network status or configuration.
  • Fetching detailed information about a particular NFT or token for display in a marketplace.
  • Checking the status of a transaction after submission to confirm success or failure.

Properties

Name Meaning
API Resource The category of blockchain data to query. Options: Account, Block, Economics, Network, NFT, Token, Transaction, Validator.
Account Action (Shown if API Resource = Account) The specific account-related query to perform. Options: Get Account, Get Balance, Get NFTs, Get Tokens, Get Transactions.
Transaction Action (Shown if API Resource = Transaction) The specific transaction-related query. Options: Get Transaction, Get Transaction Status.
Block Action (Shown if API Resource = Block) The block-related query. Options: Get Latest Block, Get Block by Hash.
Network Action (Shown if API Resource = Network) The network-related query. Options: Get Status, Get Config, Get Economics.
Token Action (Shown if API Resource = Token) The token-related query. Options: Get Token, Get All Tokens.
NFT Action (Shown if API Resource = NFT) The NFT-related query. Options: Get NFT, Get Collections.
Address (Shown if API Resource = Account) The blockchain account address to query (e.g., "erd1...").
Transaction Hash (Shown if API Resource = Transaction) The hash of the transaction to query. This is treated as sensitive input.
Block Hash (Shown if API Resource = Block and Block Action = Get Block by Hash) The hash of the block to query.
Token Identifier (Shown if API Resource = Token or NFT) The identifier of the token or NFT to query (e.g., "TOKEN-123456"). Treated as sensitive input.
Pagination Size Number of items to return for paginated queries (max 10000). Used in queries that support pagination like transactions, tokens, NFTs, validators, etc. Default is 25.
Pagination From Starting index for pagination in queries that support it. Default is 0.

Output

The node outputs JSON data corresponding to the requested API resource and action. The structure varies depending on the query but generally includes:

  • For Account queries: account details, balance info, lists of tokens, NFTs, or transactions.
  • For Transaction queries: transaction details or status.
  • For Block queries: block data such as block number, hash, timestamp, and transactions.
  • For Network queries: network status, configuration, or economics data.
  • For Token queries: token metadata or list of tokens.
  • For NFT queries: NFT details or collections.
  • For Validator queries: validator node information and staking details.
  • For Economics queries: network economic statistics.

Each output JSON object corresponds to one input item and includes the raw data returned from the MultiversX API.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for MultiversX wallet access configured in n8n.
  • Uses the official MultiversX REST API endpoints, which vary based on environment (mainnet, testnet, devnet).
  • No additional external dependencies beyond the MultiversX SDK libraries bundled internally.

Troubleshooting

  • Invalid or missing credentials: The node requires valid API authentication credentials. Ensure the API key or wallet credentials are correctly set up in n8n.
  • Invalid input parameters: Providing incorrect addresses, hashes, or token identifiers will cause errors. Double-check inputs for correctness.
  • Unsupported actions or resources: Selecting an unsupported combination of resource and action will throw errors indicating unsupported operations.
  • API rate limits or network issues: If the MultiversX API is unreachable or rate-limited, requests may fail. Check network connectivity and API usage limits.
  • Pagination parameters: Using very large pagination sizes may cause performance issues or API rejections. Keep size within reasonable limits (max 10000).

Common error messages:

  • "Unsupported API resource: ..." — means the selected resource is not implemented.
  • "Unsupported account action: ..." or similar — means the chosen action is invalid for the resource.
  • "Invalid ABI format" — not applicable here since this node does not execute smart contract calls.
  • "Private key is required but not provided" — not relevant for API Query operation.

To resolve errors, verify all input parameters, ensure correct resource-action combinations, and confirm credentials are valid.

Links and References

Discussion