Actions9
- Account Actions
- Token Actions
- Asset Actions
Overview
This node interacts with the WAX blockchain, specifically allowing users to retrieve information about a WAX account. The "Get Account Info" operation fetches detailed data related to a specified WAX account name from a given WAX blockchain API endpoint.
Common scenarios where this node is beneficial include:
- Verifying the existence and status of a WAX account.
- Retrieving account balances or resource usage details.
- Integrating WAX account data into workflows for blockchain-based applications, marketplaces, or games.
For example, a user might input an account name and the node will return the current state of that account on the WAX blockchain, which can then be used to trigger further actions or analytics.
Properties
| Name | Meaning |
|---|---|
| API Endpoint | The URL of the WAX blockchain API endpoint to query (default: https://wax.greymass.com). |
| Account Name | The WAX account name for which to retrieve information. |
Output
The node outputs JSON data containing the account information retrieved from the WAX blockchain API. This typically includes details such as account balances, permissions, resource usage, and other metadata associated with the specified WAX account.
If the node encounters an error during execution, it may output a JSON object with an error field describing the issue.
No binary data output is indicated.
Dependencies
- Requires access to a WAX blockchain API endpoint (e.g.,
https://wax.greymass.com). - Optionally uses an API key credential if configured, but not mandatory for basic account info retrieval.
- No additional external dependencies are explicitly required.
Troubleshooting
Common issues:
- Incorrect or misspelled account names will result in errors or empty responses.
- Using an invalid or unreachable API endpoint URL will cause connection failures.
- Network issues or rate limiting by the API provider may lead to timeouts or errors.
Error messages:
- Errors returned from the WAX API will be passed through in the output's
errorfield. - If the node is set to continue on failure, errors will not stop workflow execution but will be included in the output for inspection.
- Errors returned from the WAX API will be passed through in the output's
To resolve these issues:
- Verify the correctness of the account name.
- Ensure the API endpoint URL is valid and accessible.
- Check network connectivity and API usage limits.