Digital Wallet Cards icon

Digital Wallet Cards

Interact with Digital Wallet Cards loyalty program API

Overview

The node interacts with a Digital Wallet Cards loyalty program API, providing various operations across multiple resources such as cards, customers, companies, templates, communications, analytics, and system information.

Specifically, for the Analytics resource with the Get Revenue Stats operation, the node fetches revenue statistics data from the API. This is useful for businesses wanting to analyze their revenue performance over time, filtered by optional parameters like date range, company, or template.

Practical examples:

  • Retrieve total revenue generated within a specific date range.
  • Analyze revenue per company or per card template.
  • Use revenue stats to generate reports or trigger workflows based on financial performance.

Properties

Name Meaning
Additional Fields Optional filters for the revenue statistics query. Includes:
- Date From Start date for revenue statistics (ISO 8601 datetime).
- Date To End date for revenue statistics (ISO 8601 datetime).
- Company ID Numeric filter to restrict results to a specific company.
- Template ID Numeric filter to restrict results to a specific card template.

Output

The output JSON contains the revenue statistics data returned by the API endpoint /api/v2/statistics/revenue. The exact structure depends on the API response but typically includes aggregated revenue figures, possibly broken down by date, company, or template.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential configured in n8n to authenticate requests to the Digital Wallet Cards API.
  • The base URL for API requests is https://api.digitalwallet.cards.
  • The node uses internal utility functions for making HTTP requests, pagination, validation, and response transformation.

Troubleshooting

  • Missing required fields: If required filters or parameters are missing, the node will throw errors indicating which fields are mandatory.
  • API authentication errors: Ensure that the API key credential is correctly set up and has sufficient permissions.
  • Invalid date formats: Date filters must be valid ISO 8601 datetime strings; otherwise, the API may reject the request.
  • Empty or unexpected responses: Verify that the filters used actually match existing data in the system.
  • Network issues: Check connectivity to the API endpoint and proxy/firewall settings if applicable.

Links and References

Discussion