Ikoula API IKIC icon

Ikoula API IKIC

Interact with Ikoula IKIC API for account management. Developed by Ascenzia - www.ascenzia.fr
Join our community

Actions3

Overview

This node interacts with the Ikoula IKIC API to manage IKIC accounts, specifically allowing users to modify the password of an IKIC account. It is useful in scenarios where automated or programmatic management of hosting or cloud service accounts is needed, such as updating credentials securely without manual intervention.

A practical example would be a workflow that periodically updates IKIC account passwords for security compliance or resets passwords after detecting suspicious activity.

Properties

Name Meaning
Subscription ID The unique numeric identifier of the IKIC subscription/account whose password will be modified. Required for this operation.
New IKIC Password The new password string to set for the specified IKIC account. This input is treated as sensitive (password type).
Response Format The format in which the API response should be returned. Options: JSON or XML.

Output

The node outputs an array of items, each containing a json field with the API response data:

  • For successful password modification, the json field contains the API's response confirming the update.
  • If the response format is JSON, the output is parsed into an object; if XML, the raw XML string is provided under data.
  • In case of errors, the output includes an error field with the error message.

No binary data is output by this node.

Dependencies

  • Requires valid API credentials for the Ikoula API, including email and password, plus optionally a custom API URL.
  • Uses RSA public key encryption to encrypt the API password before sending requests.
  • The node performs HTTP requests to the Ikoula API endpoints.
  • Requires n8n credential configuration to provide the necessary authentication details.

Troubleshooting

  • No credentials provided!
    This error occurs if the node cannot find the required API credentials. Ensure that the API key credential is properly configured in n8n.

  • HTTP request failures
    Network issues, incorrect subscription IDs, or invalid passwords can cause request failures. Verify the subscription ID exists and the new password meets any API requirements.

  • Response format issues
    Selecting XML format returns raw XML strings, which may require additional parsing downstream.

  • Encryption errors
    The node encrypts the API password using a hardcoded RSA public key. If this key changes or is invalid, requests will fail. Confirm the public key matches the API server expectations.

Links and References

Discussion