Qlik Sense on Windows Help for Developers

Use Qlik Sense APIs and tools to build, extend and deploy custom data-driven applications. You can also build mashups, create apps and visualizations on the fly, or embed rich and engaging analytics into your applications.

Developing for Qlik Cloud?

Check out the site Qlik Developer instead.

What's new

Learn about new features and improvements.

API governance

The API governance policy include guidelines around the stability of the APIs and how to handle deprecation of existing APIs.

APIs for Qlik Sense Enterprise on Windows

Use Qlik Sense APIs on Windows to automate jobs like creating and triggering tasks, applying licenses, and uploading extensions.

Get started with APIs on Windows

Start using Qlik Sense APIs on Windows.

API reference for Windows

See all of the APIs that you can use within Qlik Sense Enterprise on Windows.

How to use the APIs

Build your first mashup, and extension for Qlik Sense. Explore how you can do more with Qlik Sense APIs, and more.

Working with mashups

See the many ways that you can work with mashups in Windows and Qlik Sense SaaS.

Working with extensions

Create visualization extensions to extend the visualization capabilities of Qlik Sense by using standard Web technologies.

Building customized connectors

Build customized connectors, used to retrieve data from data sources not supported by a generic Qlik Sense installation.

Building Windows applications

Use the .NET SDK to integrate Qlik Sense in your own Windows (.NET) applications.

Tools and development kits

Dev Hub

Use the Dev Hub to build mashups, and visualization extensions.

Qlik Sense .NET SDK

The Qlik Sense .NET SDK contains components for embedding Qlik Sense into host application programs developed by software manufacturers on an OEM basis.

QVX SDK

Use the QVX SDK to build customized connectors, used to retrieve data from data sources not supported by a generic Qlik Sense installation.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!

Leave your feedback here