Ikoula API Microsoft icon

Ikoula API Microsoft

Interact with Ikoula Microsoft API for Microsoft 365 account management. Developed by Ascenzia - www.ascenzia.fr

Overview

This node interacts with the Ikoula Microsoft 365 API to manage Microsoft 365 licences, specifically allowing termination of licences associated with a Microsoft subscription. It is useful in scenarios where an organization needs to reduce the number of active licences or cancel unused licences to optimize costs and maintain compliance.

For example, if a company wants to terminate a certain number of Microsoft 365 licences from their subscription because some employees have left, this node can be used to specify which licence and how many should be terminated.

Properties

Name Meaning
Subscription ID The numeric ID of the Microsoft subscription under which the licence exists.
Licence ID The identifier string of the specific licence to terminate.
Quantity The number of licences to terminate (must be a positive integer).
Response Format The format in which the API response will be returned. Options: JSON, XML.

Output

The node outputs the response from the Ikoula Microsoft API after attempting to terminate the specified licence(s). The output is available in the json field and contains either:

  • A JSON object representing the API response when the response format is set to JSON.
  • A string containing XML data when the response format is set to XML.

No binary data output is produced by this operation.

Dependencies

  • Requires valid credentials for the Ikoula Microsoft API, including an email, password, and API URL.
  • The password is encrypted using RSA public key encryption before being sent.
  • The node makes HTTP requests to the Ikoula API endpoint (https://api.ikoula.com by default).
  • Proper configuration of the API credentials within n8n is necessary for successful authentication.

Troubleshooting

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

  • Invalid Licence ID or Subscription ID
    If the licence or subscription IDs are incorrect or do not exist, the API may return errors or fail silently. Verify these IDs before running the node.

  • Quantity exceeds available licences
    Attempting to terminate more licences than currently assigned may cause API errors. Confirm the quantity is valid.

  • API connectivity issues
    Network problems or incorrect API URLs can cause request failures. Check network access and API endpoint correctness.

  • Response format mismatch
    Selecting XML format requires handling XML responses downstream; otherwise, JSON is recommended for easier processing.

Links and References

Discussion