Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Accepted Solutions
Hey,
So let's break it down into the two different scenarios.
1. Reloading Applications
The management of the platform, user access control, provisioning of applications and data reload are done through what the refer to as the Qlik Repository Service API. This is a REST based api so any programming language that is able to execute HTTP requests and parse JSON will be able to integrate with it.
2. Embedding Analytics
Embedding Qlik Sense charts into other systems is done through the client, either in a web browser or in a web control or some sort. Since this integration happens client side and in the context of a browser we provide javascript apis to embed charts and analytic objects into your system. So you can still serve up your application using Java or Scala but the actual client side integration happens in the browser so the domain language would be Javascript.
These Javascript APIs are refered to as Capabilities API in the documentation.
3. (which you didn't ask for 
) Communicating with the Qlik Engine
If you do not wish to leverage any Qliks visual components but instead leverage our on-demand, in-memory calculation engine you would leverage the Engine API. The Engine API is a protocol that defines how the communication between clients and the Engine should take place. So as long as your programming language supports WebSockets and JSON then you can initiate communication with the Qlik Engine, if you want to perform batch, server-side tasks or building your own client.
I hope that made things a little bit easier to understand
Hey,
So let's break it down into the two different scenarios.
1. Reloading Applications
The management of the platform, user access control, provisioning of applications and data reload are done through what the refer to as the Qlik Repository Service API. This is a REST based api so any programming language that is able to execute HTTP requests and parse JSON will be able to integrate with it.
2. Embedding Analytics
Embedding Qlik Sense charts into other systems is done through the client, either in a web browser or in a web control or some sort. Since this integration happens client side and in the context of a browser we provide javascript apis to embed charts and analytic objects into your system. So you can still serve up your application using Java or Scala but the actual client side integration happens in the browser so the domain language would be Javascript.
These Javascript APIs are refered to as Capabilities API in the documentation.
3. (which you didn't ask for ) Communicating with the Qlik Engine
If you do not wish to leverage any Qliks visual components but instead leverage our on-demand, in-memory calculation engine you would leverage the Engine API. The Engine API is a protocol that defines how the communication between clients and the Engine should take place. So as long as your programming language supports WebSockets and JSON then you can initiate communication with the Qlik Engine, if you want to perform batch, server-side tasks or building your own client.
I hope that made things a little bit easier to understand
