Namespaces for REST and Events APIs are being introduced in Qlik Cloud to support the growing number of APIs and services in the platform, and to unlock versioning support in the future. This change makes it easier for you to find, understand, and use Qlik APIs by grouping related resources by context, as well as standardizing the interface for the APIs.
To learn more, see theAPI namespaces overview pageon qlik.dev.
What to expect
The new namespaced APIs will be introduced in parallel with the existing APIs.
The existing APIs will be deprecated and removed after aminimum12-month deprecation period from the notice of deprecation on thechangelog(qlik.dev).
No immediate action is needed. As each API is namespaced, a deprecation notice will be published with migration guides.
Key changes
REST
Removal ofv1from the path:v1will be removed from the path to prepare for versioning support in the future.
Grouping resources by context: Related APIs will be grouped together under a namespace which indicates in which context the resources are applicable. For example:
Theanalyticsnamespace for Analytics-specific resources such as apps, notes, and ODAGs apps.
Thecorenamespace for platform-wide resources such as users, groups, ip-policies, and roles.
Standardization of interfaces: The payloads for the new namespaced APIs will be standardized to be compliant with Qlik’s API design principles, meaning improved consistency of payloads, query parameters, and response formats between different APIs, irrespective of the context.
Events
Events will adhere to the same namespace rule to avoid conflict of resource names and to match the REST resources. This changes the pattern fromcom.qlik.v<version>.<eventContext>.<action>tocom.qlik.<namespace>.<eventContext>.<action>.
Want to learn more?
Head to theAPI namespaces overview pagefor additional details and examples.
Thank you for choosing Qlik,Qlik Support
...View More
QlikData Gateway - Direct Accessversions 1.4 and 1.5 are reaching End of Life by January 31st, 2026*.
The original announcement can be read inDirect Access gateway versions 1.4 and 1.5 reaching End of Life by January 31st, 2026.
How will this affect me?
Both versions will stop working after reaching End of Life. We recommend you plan to upgrade to the latest available version of the currently supported 1.7.x as soon as possible.
How do I upgrade?
For the upgrade procedure, please refer toUpgrading Qlik Data Gateway - Direct Accesson Qlik's online help. This page also lists all the significant changes for each version.
The upgrade to 1.7.x from 1.4 or 1.5 has been thoroughly tested, and the process is expected to be smooth. However, please follow the steps carefully and always take a backup before upgrading. It is also worth noting that .NET 8.x is required (from v1.6.6) and will be automatically installed during the upgrade.
What else do I need to keep in mind?
Several configuration settings were added in later versions of the Direct Access gateway that may apply to your deployment. Therefore, please review all details in the online help onConfiguring and troubleshooting Qlik Data Gateway - Direct Access. Note that most Direct Access gateway settings can be configured in the Qlik Cloud Administration activity center (from v1.7.2).
Always upgrade to the latest version!
If you have questions or need additional assistance,our forumsare always open to you, and Support is only a chat away.
Thank you for choosing Qlik,Qlik Support
* The previously announced date was set for December 31st, 2025, and was later extended until January the following year.
...View More
Several Qlik Reporting blocks will be deprecated on February 25th, 2026. Automation developers will notice the following blocks reflecting their deprecated status:
Get Chart Image (Deprecated)
GetPixelPerfect(Deprecated)
Get Tabular Report (Deprecated)
What does this mean for me?
Review if you have any of the deprecated blocks in use and update them to their new variants as soon as possible.
When updating the blocks, automation developers should note that there are changes to the error handling between the corresponding blocks.
Refer to the API specifications Response 200 > application/JSON for results and reasons deprecation status.
Any exception management logic will need to be adjusted in line with the API specifications as documented inGet report request outputs
If you have any questions, we're happy to assist. Reply to this blog post or take your queries to our Support Chat.
Thank you for choosing Qlik,Qlik Support
...View More
Dear Qlik Users,
The Qlik Support Portal File Share service will undergo maintenance on December 6th, 2025.
How am I impacted?
During the maintenance,https://files.qlik.com will be unavailable. This will temporarily disable the ability to share log files and other material with Qlik Support.
When will the maintenance happen?
On December 6th, 2025. Begins at 4:30 AM EST and ends at 8:30 AM, with an expected duration of four hours.
Timetable with local time zones:
Time Zone
Start Time
Finish Time
EST
4:30 AM
8:30 AM
CET
10:30 AM
2:30 PM
IST
3 PM
7 PM
Thank you for choosing Qlik,Qlik Support
...View More
Hello Qlik Users,
As announced previously (see Qlik Automate execution token changes),execution tokens will become header parameters on February 1st, 2026.
When triggering a triggered automation through the trigger URL (see the endpoint below),the execution token must be sent as a header parameter.Currently, it is possible to send the execution token as a query parameter. Starting February 1st, 2026, sending execution tokens as header parameters will be enforced.
api/v1/automations/{id}/actions/execute
Don't hesitate to reach out if you have any questions or address our experts directly in theQlik Automateforum.
Thank you for choosing Qlik,Qlik Support
...View More
Don't miss our next Q&A with Qlik!Hear from our panel of experts to help you get the most out of your Qlik experience.
WATCH RECORDING HERE
...View More
The following two items were deprecated in June 2025:
Developer role
Enable API keys toggle
The deprecation notice was communicated in anAdministration announcementand documented on ourWhat's New in Qlik Cloudfeed. SeeDeveloper role and API key toggle deprecated | 6/16/2025for details.
Following the deprecation, theDeveloper roleandthe Enable API keys togglewill be removed in the coming weeks, in line with the original announcement,aiming for the end of 2025.
For more information, see Qlik Cloud: Removing the deprecated Developer role and Enable API keys toggle (November 2025).
If you have any questions, we're happy to assist. Reply to this blog post or take your queries to our Support Chat.
Thank you for choosing Qlik,Qlik Support
...View More
Hi everyone, Want to stay a step ahead of important Qlik support issues? Then sign up for our monthly webinar series where you can get first-hand insights from Qlik experts.
The session from November looked at Building on Iceberg with Qlik Open Lakehouse.
But wait, what is it exactly?Techspert Talks is a free webinar held on a monthly basis, where you can hear directly from Qlik Techsperts on topics that are relevant to Customers and Partners today.
In this session we will cover:
Benefits of Iceberg Lakehouse
How to build an Open Lakehouse
Mirroring
Watch the recording
...View More
Dear Qlik Replicate customers,
Salesforce announced (October 31st, 2025) that it is postponing the deprecation of theUse Any API Clientuser permission. SeeDeprecating "Use Any API Client" User Permissionfor details.
Qlik will keep the OAUT plans on the roadmap to deliver them in time with Salesforce's updated plans.
Salesforce has announced the deprecation of theUse Any API Clientuser permission. For details, seeDeprecating "Use Any API Client" User Permission | help.salesforce.com.
We understand that this is a security-related change, and Qlik is actively addressing it by developing Qlik Replicate support forOAuth Authentication. This work is a top priority for our team at present.
If you are affected by this change and have activated access policies relying on this permission, we recommend reaching out to Salesforce to request an extension. We are aware that some customers have successfully obtained an additional month of access.
By the end of this extension period, we expect to have an alternative solution in place using OAuth.Customers using the Qlik Replicate tool to read data from the Salesforce source should be aware of this change.
Thank you for your understanding and cooperation as we work to ensure a smooth transition.If you have any questions, we're happy to assist. Reply to this blog post or take your queries to our Support Chat.
Thank you for choosing Qlik,Qlik Support
...View More
