Ikoula API CS icon

Ikoula API CS

Interact with Ikoula CloudStack API for billing and consumption. Developed by Ascenzia - www.ascenzia.fr

Overview

This node interacts with the Ikoula CloudStack API to list billing information related to a subscription. Specifically, the "List Bills" operation retrieves all bills associated with a given subscription ID. This is useful for users who want to programmatically access their billing data from Ikoula's cloud services, enabling automation of financial reporting, auditing, or integration with other accounting systems.

Practical examples include:

  • Automatically fetching monthly bills for a subscription to generate custom invoices.
  • Integrating billing data into dashboards for real-time cost monitoring.
  • Exporting billing details to external systems for further analysis.

Properties

Name Meaning
Subscription ID The unique numeric identifier of the subscription whose bills you want to list.
Response Format The format in which the API response should be returned. Options: JSON or XML.

Output

The node outputs an array of items where each item contains a json field holding the API response data.

  • If the response format is JSON, the json field will contain a parsed JavaScript object representing the bills data.
  • If the response format is XML, the json field will contain the raw XML string under a property named data.

No binary data output is produced by this node.

Example JSON output snippet (simplified):

{
  "json": {
    "bills": [
      {
        "billId": 12345,
        "amount": 100.0,
        "date": "2024-05-01",
        ...
      },
      ...
    ]
  }
}

Dependencies

  • Requires valid credentials for the Ikoula API, including email, password, and optionally a custom API URL.
  • The password is encrypted using RSA public key encryption before being sent.
  • The node makes HTTP GET requests to the Ikoula API endpoints.
  • No additional environment variables are required beyond the configured credentials.

Troubleshooting

  • No credentials provided!
    This error occurs if the node is executed without setting up the required API credentials. Ensure that the API authentication details are correctly configured in n8n.

  • HTTP request failures
    Network issues, invalid subscription IDs, or incorrect API URLs can cause request errors. Verify the subscription ID is correct and the API endpoint is reachable.

  • Response format issues
    If XML is selected but downstream nodes expect JSON, parsing errors may occur. Choose the response format according to your workflow needs.

  • Continue on Fail behavior
    If enabled, the node will continue processing subsequent items even if one fails, returning error messages in the output JSON.

Links and References


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

Discussion