Digital Wallet Cards icon

Digital Wallet Cards

Interact with Digital Wallet Cards loyalty program API

Overview

The node interacts with the Digital Wallet Cards API, providing various operations across multiple resources such as cards, customers, companies, templates, communications, analytics, and system-level functions. Specifically for the System resource and the Get Usage Stats operation, the node fetches API usage statistics within an optional date range.

This operation is useful for monitoring and analyzing how the API is being used over time, which can help in managing quotas, understanding traffic patterns, or auditing usage.

Example use case:
A user wants to retrieve the number of API calls made between two dates to monitor their usage limits or generate reports on API consumption.

Properties

Name Meaning
Additional Fields Optional fields to refine the request:
- Date From Start date/time to filter usage statistics (optional)
- Date To End date/time to filter usage statistics (optional)

These properties allow specifying a date range to limit the usage statistics returned by the API.

Output

The output JSON contains the usage statistics data returned from the API endpoint /api/v2/statistics/usage. The structure typically includes aggregated metrics about API usage, such as counts of requests, possibly broken down by time intervals or categories.

Since this is a system-level statistics call, no binary data is involved.

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 handling, input validation, and response transformation.

Troubleshooting

  • Missing required parameters: If required fields like tariffId or operationId are missing for other system operations, the node will throw errors indicating which fields are missing.
  • Invalid date formats: Ensure that Date From and Date To are valid ISO8601 date strings; otherwise, the API may reject the request.
  • API authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
  • Empty results: If no usage stats exist for the specified date range, the output may be empty or minimal.
  • Unknown operation error: If an unsupported operation is selected, the node throws an error indicating the unknown operation.

Links and References


If you need details on other operations or resources, feel free to ask!

Discussion