CloudAlly icon

CloudAlly

Work with the CloudAlly API

Actions5

Overview

This node integrates with the CloudAlly API, specifically targeting the "Bill" resource with the "Get Many" operation. It allows users to retrieve multiple billing records or invoices related to resellers managed within the CloudAlly platform. This is useful for scenarios such as generating reports on reseller billing, auditing charges, or synchronizing billing data with other financial systems.

For example, a user might employ this node to fetch all bills associated with a particular reseller over a given period to analyze revenue or verify billing accuracy.

Properties

Name Meaning
Resource Type The type of resource to interact with. Options: Reseller (targets reseller-related data).

Note: In this context, only the "Reseller" option is available for the Resource Type, which directs requests to the reseller-specific endpoint of the CloudAlly API.

Output

The node outputs JSON data representing the collection of billing records retrieved from the CloudAlly API. Each item in the output corresponds to a bill or invoice associated with a reseller. The structure typically includes details such as billing dates, amounts, and related metadata.

If the API supports binary data (e.g., PDF invoices), the node would include this in the binary output field; however, based on the provided code, the primary output is JSON-formatted billing information.

Dependencies

  • Requires an API key credential for authenticating with the CloudAlly API. This includes:

    • An access token
    • A client ID
    • A client secret

  • The node uses the base URL https://api.cloudally.com/v2 by default, with a specialized base URL for reseller resources (https://api.cloudally.com/v2/resellers).

  • Pagination support is implemented via a utility function to handle large result sets.

Troubleshooting

  • Authentication Errors: If the node fails due to authentication issues, verify that the API credentials (access token, client ID, client secret) are correctly configured and have not expired.

  • Incorrect Resource Type: Since only "Reseller" is supported, selecting an unsupported resource type will cause errors or no data returned.

  • API Rate Limits: Exceeding CloudAlly API rate limits may result in temporary failures. Implement retry logic or reduce request frequency.

  • Pagination Issues: Large datasets require proper pagination handling. Ensure the pagination settings are correctly applied to avoid incomplete data retrieval.

Links and References

Discussion