
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
How Can I Allow End Users to Use my REST API calls??
Hello all,
Any help or advice would mean the world!!
I created a Qlik app in Qlik Sense Enterprise and was able to create a REST API POST connection that triggers a Databricks job(the REST connection uses an access token i created from Databricks) to run with dynamic selections made by the user. Databricks performs some transformations on the data with the parameters sent from Qlik and I then utilize an Apache Spark Connector to read the data back into the app.
Current methodology: I as the developer can open the app that has a default dataset already loaded. I then make some selections in a couple of filters and click a button called "Load Data". This button sets my selections as variables first and then finally, performs a Load Data action that initiates the REST API call (first action in the qlik load editor) to send my inputs to Databricks and then loads the transformed data back with an apache spark connector(which i also have to give users access to).
The Problem: I can obviously do this myself since I have access to Databricks and it is my REST API connection, but I need make sure users(there will be potentially hundreds) that are using this dashboard will have a seamless way of sending their own inputs through the REST API post method. Is there a way I can somehow change my current configuration so any user with access to the dashboard can utilize its connections? Or anything else?
I have attached my current configuration of my REST API Connector for context:
- Subscribe by Topic:
-
API
-
Client Managed
-
Connector
-
Extension
-
General Question
-
Integration
-
Qlik Sense

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I understand the problem. The issue is that the users can not alter the document variable on a published app . Any changes to a variable is only locally for the users user interface and will not be Forwarded to the reload script when assuming .
One solution is to make the app available for duplication, meaning that each user can duplicate the app and have it available in their own work stream.
Note that only users with professional license will be able to edit apps or reload tasks. These features are blocked for analyzer users.
Qlik Community MVP

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Another possible way to solve this is to look into app on demand generation (ODAG). Where users can trigger a reload of a template app based on selection in a selection app.
I'm unsure if you can forward variable values or not, but you could in many cases be able to do a workaround by adjusting your data model in the selection app to fit your need.
Qlik Community MVP
