Ikoula API ESET icon

Ikoula API ESET

Interact with Ikoula ESET API for ESET antivirus services management. Developed by Ascenzia - www.ascenzia.fr
Join our community

Actions2

Overview

This node integrates with the Ikoula ESET API to manage ESET antivirus services. It allows users to either list all ESET accounts or retrieve details of a specific ESET account subscription. This is useful for IT administrators or managed service providers who need to automate the management and monitoring of multiple ESET antivirus subscriptions through Ikoula’s platform.

Practical examples:

  • Automatically fetching a list of all ESET antivirus accounts under your organization to audit active subscriptions.
  • Retrieving detailed information about a particular ESET subscription by its ID to check status or configuration.

Properties

Name Meaning
Response Format The format in which the API response will be returned. Options: JSON, XML.

Output

The node outputs an array of JSON objects, each corresponding to one input item processed. The main output field is:

  • json: Contains the parsed API response data.
    • If the response format is JSON, this will be a JavaScript object representing the API response.
    • If the response format is XML, the raw XML string is returned inside the data property of the json object.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential (email and password) for authenticating with the Ikoula ESET API.
  • The password is encrypted using RSA public key encryption before being sent.
  • The base URL for the API defaults to https://api.ikoula.com but can be overridden via credentials.
  • The node uses HTTP GET requests to interact with the API endpoints.

Troubleshooting

  • No credentials provided!
    This error occurs if the required API authentication credentials are missing. Ensure you have configured the API key credential with valid email and password.

  • API request failures:
    Network issues, invalid credentials, or incorrect subscription IDs may cause HTTP errors. Check that the subscription ID exists and credentials are correct.

  • Response format issues:
    If XML is selected as the response format, downstream nodes expecting JSON might fail. Make sure to handle XML responses appropriately or use JSON format.

  • Encryption errors:
    The password is encrypted with a hardcoded RSA public key. If this key changes on the server side, authentication will fail until the node is updated.

Links and References

Discussion