API Reference

AlisQI Developer portal

AlisQI is a modern, cloud-based, no-code Quality Management System (QMS) designed to be an integral part of your enterprise IT landscape. In today’s data-driven manufacturing environments, no application should operate in isolation. By integrating AlisQI with your broader IT ecosystem — ERP, MES, PLM, LIMS, instruments, sensors, or even your corporate website — you enable a seamless, data-driven approach to quality and operations.

Why Integration Matters

Integrating your QMS with your other business systems unlocks tremendous value. It ensures data consistency, process automation, and real-time insights across the value chain. For example:

  • Synchronizing master data from ERP ensures all systems use the same definitions for materials, customers, and specifications.
  • Connecting manufacturing orders and batch releases streamlines production quality checks and traceability.
  • Integrating with PLM or LIMS systems centralizes product specifications and test results.
  • Feeding quality data into BI tools or data lakes powers predictive analytics and continuous improvement initiatives.

Ultimately, integration reduces manual effort, eliminates data silos, and strengthens decision-making across departments.

The Modern Integration Vision: Middleware and iPaaS

At AlisQI, we believe modern businesses should embrace middleware or Integration Platform as a Service (iPaaS) solutions as the backbone of their digital architecture. These platforms simplify connectivity, orchestration, and monitoring across multiple systems — especially in complex environments where you need to integrate dozens of applications, sensors, or data sources.

AlisQI provides standard APIs and connectors that seamlessly integrate with leading iPaaS solutions. Once connected, AlisQI becomes a first-class citizen in your automation and data workflows — allowing IT teams to build and manage integrations without custom code.

Commonly used platforms include:

These middleware solutions empower your business to innovate faster, reduce integration complexity, and future-proof your IT landscape.

Read more about iPaaS in our blog post

If you do not have a middleware or iPaaS solution available, you can always interact with our API directly.

Open, Secure, and Flexible API

The AlisQI API follows the OpenAPI v3.1 specification and is built on modern, secure web standards. It enables full access to data and processes within AlisQI, letting you design integrations that precisely fit your business needs. From master data synchronization to instrument connectivity and reporting, the API supports every step in your digital quality workflow.

Download the OpenAPI v3.1 specification of the AlisQI API here (JSON).

Example integrations include:

  • Master data synchronization from ERP
  • Manufacturing orders and batch releases
  • Specification management between PLM and AlisQI
  • Quality data exports to ERP or BI environments (Connect with Power BI)
  • Instrument and SCADA integrations for automated data capture

Case in point: Berry Global connected AlisQI with WinCC using just 10 lines of code — a testament to the flexibility and openness of our API.

Security and Single Sign-On (SSO)

Integration shouldn’t compromise security. AlisQI supports Single Sign-On (SSO) to simplify access management and improve security across systems. We make SSO available free of charge for all customers, ensuring that integration and security go hand in hand.

This documentation describes the AlisQI Technical platform and Security policies.

👍

As we highly value security in all of our operations, we decided to make SSO available for all AlisQI customers free of charge!

API Rate Limits & Versioning

Rate Limits

The AlisQI API operates under a fair-use policy that includes usage rate limits. These safeguards protect platform performance, prevent system overload, and help ensure a stable experience for all users.
You can find detailed information about current operational limits in the Operational Limits section of this development portal.

Backwards Compatibility

We follow industry best practices to maintain a stable and predictable API. All new features and enhancements are introduced with backwards compatibility in mind.
If a breaking change becomes necessary, it will be released under a new version namespace (e.g., v2, v3) so existing integrations can continue to function without interruption.