Actions9
- Account Actions
- Token Actions
- Asset Actions
Overview
This node allows users to interact with the WAX blockchain by sending requests to a specified WAX API endpoint. It is useful for automating blockchain-related tasks such as querying blockchain data, submitting transactions, or retrieving account information on the WAX network. Practical examples include fetching token balances, checking transaction statuses, or pushing new actions to the blockchain.
Properties
| Name | Meaning |
|---|---|
| API Endpoint | The URL of the WAX blockchain API endpoint to which requests will be sent. Default is https://wax.greymass.com. This should point to a valid WAX node API. |
Output
The node outputs JSON data representing the response from the WAX blockchain API for each input item processed. The structure of the output depends on the specific operation performed but generally contains blockchain data such as transaction details, account info, or query results.
If an error occurs during execution and "Continue On Fail" is enabled, the output for that item will contain a JSON object with an error field describing the issue.
No binary data output is produced by this node.
Dependencies
- Requires access to a WAX blockchain API endpoint (configurable via the "API Endpoint" property).
- Optionally supports authentication via an API key credential (referred to generically as a private key credential) if needed by the endpoint.
- No additional external dependencies are bundled within the node code.
Troubleshooting
- Common issues:
- Incorrect or unreachable API endpoint URL will cause request failures.
- Missing or invalid authentication credentials if the endpoint requires them.
- Network connectivity problems when connecting to the WAX API.
- Error messages:
- Errors returned from the blockchain API will be propagated in the output unless "Continue On Fail" is enabled.
- Typical errors include timeouts, unauthorized access, or malformed requests.
- Resolutions:
- Verify the API endpoint URL is correct and accessible.
- Ensure any required API keys or authentication tokens are properly configured.
- Check network connectivity and firewall settings.