Skip to content
  • There are no suggestions because the search field is empty.

Application integration with Make.com

AlisQI API

The AlisQI API allows any developer to read and write all master and transactional data. The endpoints of our API support our dynamic data model. This enables you or any developer you hire, to create custom integrations with your self-defined AlisQI setup.

Read all about the AlisQI API here.

To connect services, transform data or schedule operations, we suggest you to use a middleware tool. Otherwise, you’ll find yourself building custom integrations for each and every tool you deploy.

If you have no middleware in place yet, you might want to evaluate Make.com

Make

Make is a tool that helps you to automate manual processes, without the need to write code. They refer to themselves as ‘the glue of the internet’, helping their customers to connect together apps and services.

To understand how Make works, you need to know what an API is. An API (application program interface) is something that a software provider (like AlisQI) provides so developers can access data within their applications. For example, a developer writes code that detects all new sensor data from an instrument and writes that to AlisQI.

Instead of needing the code, Make has turned these complicated APIs into simple blocks that can be connected with a simple drag-and-drop. Make calls these blocks ‘Modules’ and the visual connections between them ‘Scenarios’.

Once set up, Make runs 24-7, processing in the background with no maintenance required.

AlisQI is available as standardized app within the Make ecosystem. Consult AlisQI support to get you up and running with the AlisQI app in Make.

Picture1-3

Security

Any system integration deals with your important data. And thus, its security should be validated.

All AlisQI API calls are subject to encryption and authentication. All API calls are send over HTTPS, securing the data transfer. In order to invoke the AlisQI API endpoints, developers need to create an authentication token. Each token is connected to a single user. The READ/WRITE permission this user has for analysis-sets (via its user group), also apply to the API invocations.

When deploying a middleware solution, being it Make or any other platform, that platform will process your data and should thus be secured as well.

We validated the Make security policies before selecting this as a valid tool for us. However, you need to do your own assessments. To support your assessment, we summarized the main security features of the Make platform: