API comparison between products

Whether you’re building solutions for Qlik Sense client managed (Windows) or Qlik Cloud, many of the APIs are cross-compatible and work with either deployment. However, there are some subtle differences, or unavailable methods in the cloud you want to know about.

The list below indicates if the API is compatible with client managed editions of Qlik Sense, compatible on Qlik Cloud, and if there are any differences to expect.

In general, almost all of the APIs related to embedding visualizations are compatible across products with minor modifications to authentication and cross-site origin handling. For specific client-managed APIs like the Repository Service API and the Proxy API, refer to the known differences to understand the way these APIs are represented in Qlik Cloud.

Most Popular

API	Client-managed Compatible	Cloud Compatible	Known Differences
App Integration API	YES	YES
Visualization API	YES	YES
Engine JSON API	YES	YES	ExportData method disabled in Cloud, replaced by Reporting Services API
Backend API	YES	YES	Refer to the client-managed documentation for using the Backend API with Qlik Cloud
qlik-cli	YES	YES	The qlik-cli for Qlik Cloud does have support for many Client-managed Repository service API endpoints. However, if you require the full compliment of REST endpoints available for Client-managed editions of Qlik Sense, please follow the Client managed link.

Capability APIs

API	Client-managed Compatible	Cloud Compatible	Known Differences
Root API	YES	YES	Refer to the client-managed documentation for using the Root API with Qlik Cloud callRepository method (deprecated) getAppList method is replaced by the items API in Qlik Cloud using the resource type query string parameter equal to app getExtensionList method is replaced by the Extensions REST API in Qlik Cloud. Returns a list for the tenant, not the app. getGlobal method is not available in Qlik Cloud. Engine connections in cloud require a Qlik Sense application. sessionApp method is not available in Qlik Cloud through Root API. Use enigma.js instead. sessionAppFromApp method is not available in Qlik Cloud through Root API. Use enigma.js instead.
Field API	YES	YES
Navigation API	YES	YES
Table API	YES	YES
Variable API	YES	YES

Libraries and Tools

API	Client-managed Compatible	Cloud Compatible	Known Differences
qlik-cli	YES	YES	The qlik-cli for Qlik Cloud does have support for many Client-managed Repository service API endpoints. However, if you require the full compliment of REST endpoints available for Client-managed editions of Qlik Sense, please follow the Client managed link.
enigma.js	YES	YES
nebula.js	YES	YES
leonardo-ui	YES	YES

Client-managed specific

API	Client-managed Compatible	Cloud Compatible	Known Differences
QVX SDK	YES	NO
Repository API	YES	NO	On Qlik Cloud, management APIs are separated into their own resources. Learn more here.
Proxy API	YES	NO	Refer to the identity providers API for configuring authentication options in Qlik Cloud. Refer to JWT authorization to integrate authorization to Qlik Cloud into your applications.
ODAG Service API	YES	NO
Natural Language Query API	YES	NO
User Directory Connector API	YES	NO
About Service API	YES	NO