Ikoula HEB API icon

Ikoula HEB API

Interact with Ikoula HEB API for web hosting services management. Developed by Ascenzia - www.ascenzia.fr
Join our community

Actions2

Overview

This node integrates with the Ikoula HEB API to manage web hosting services. Specifically, for the "HEB" resource and the "List Accounts" operation, it retrieves a list of all HEB accounts associated with the authenticated user. This is useful for users who want to programmatically access their web hosting account information, automate monitoring, or integrate account data into other workflows.

Practical examples:

  • Automatically fetching all hosting accounts to generate reports.
  • Syncing account lists with external dashboards or CRMs.
  • Triggering downstream processes based on the number or status of hosting accounts.

Properties

Name Meaning
Response Format The format of the API response. Options: JSON (default) or XML. Determines how data is returned from the API.

Output

The node outputs an array of items where each item contains a json field representing the API response:

  • If the response format is JSON, the json field contains the parsed JSON object representing the list of HEB accounts.
  • If the response format is XML, the json field contains the raw XML string under a data property.

Each output item corresponds to one input item processed by the node, paired accordingly.

No binary data output is produced by this operation.

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 endpoint /heb.
  • The node expects the API to support both JSON and XML response formats.

Troubleshooting

  • No credentials provided!
    Error thrown if the required API credentials are missing. Ensure that the node has been configured with valid authentication details.

  • HTTP request failures:
    Network issues, invalid credentials, or incorrect API URLs can cause request errors. Verify connectivity and credential correctness.

  • Response parsing issues:
    If the response format is set to XML but downstream nodes expect JSON, parsing errors may occur. Choose the appropriate response format based on your workflow needs.

  • Continue On Fail behavior:
    If enabled, the node will continue processing subsequent items even if some fail, returning error messages in the output JSON.

Links and References

Discussion