Voltage icon

Voltage

Interact with Voltage API
Join our community

Actions18

Overview

This node interacts with the Voltage API to retrieve the transaction history (ledger) of a specific wallet within an organization. It is useful for scenarios where you need to audit, analyze, or monitor all transactions associated with a particular wallet, such as tracking payments, deposits, and withdrawals over time.

Practical examples include:

  • Fetching recent wallet transactions to display in a financial dashboard.
  • Auditing wallet activity for compliance or accounting purposes.
  • Filtering wallet ledger entries by date range or sorting order to generate reports.

Properties

Name Meaning
Organization ID The unique identifier of the organization that owns the wallet.
Wallet ID The unique identifier of the specific wallet whose ledger (transaction history) is requested.
Filters Optional filters to refine the ledger results:
- Limit Maximum number of ledger entries to return (default 50).
- Offset Number of ledger entries to skip before starting to collect results (default 0).
- Start Date Only include ledger entries after this date/time.
- End Date Only include ledger entries before this date/time.
- Sort Key Field to sort the results by; options are "Created At" or "Updated At" (default "Created At").
- Sort Order Sort direction; either "Ascending" or "Descending" (default "Descending").

Output

The output JSON contains the wallet ledger data returned from the Voltage API. This typically includes an array or object representing individual ledger entries, each describing a transaction related to the wallet. Each entry may contain details such as transaction amount, type, timestamp, status, and other metadata relevant to the wallet's transaction history.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Voltage API.
  • The node uses the Voltage API SDK client configured with the API key, base URL, and timeout settings.
  • Proper configuration of the organization ID and wallet ID is necessary to fetch the correct ledger data.

Troubleshooting

  • Common Issues:

    • Invalid or missing API key can cause authentication errors.
    • Incorrect organization ID or wallet ID will result in "Not Found" errors.
    • Providing invalid filter parameters (e.g., malformed dates) may cause validation errors.

  • Error Messages:

    • Validation Error (422): Indicates invalid request data; check parameter formats and required fields.
    • Authentication Error (401): API key is invalid or missing; verify credentials.
    • Permission Error (403): API key lacks permission to access the resource; check API key scopes.
    • Not Found (404): Organization or wallet does not exist; confirm IDs.
    • Server Error (5xx): Temporary issues with the Voltage API; retry later.
    • Failed to parse response as JSON: Usually indicates authentication failure or incorrect organization ID; verify credentials and IDs.

Links and References

Discussion