Qlik Cloud Error: 401 Authorization Required after removal of deprecated Developer role and Enable API keys toggle

[Sonja_Bauernfeind]

Updated 4th of February, 2026: the role and keys toggle has been removed as announced.

The following two items were deprecated in June 2025 and removed in February 2026:

• Developer role
• Enable API keys toggle

This can lead to Error: 401 Authorization Required when executing third party API calls.

What actions do I need to take?

To replace the deprecated built-in role, migrate your users away from the Developer role to a Custom Role with the required permissions (Manage API Keys).

To create and assign a replacement custom role:

1. In the Administration activity center, go to Manage users
2. On the Permissions tab, select Create new
3. Name the new custom role using your organization's naming convention.
   For example: "AllowManageAPIKeys"
4. Expand Features and Actions
5. Then expand Developer
6. Set Manage API keys to Allowed and press 'confirm' to  complete the creation of the new custom role
7. In the same screen, click the dropdown menu on the right side of the screen.
8. Use the Assign button feature to find and assign the new custom role to specific users or groups. Do so specifically for those who previously had the now deprecated Developer role
9. Remove the deprecated role from those users or groups

For additional reading on the Managed API Keys (set to Not allowed by default), see Permissions in User Default and custom roles | Permission settings — Features and actions.

When were the deprecated items removed?

The Developer role and Enable API keys toggle were removed in February 2026. 

What will happen if we fail to migrate?

Once the Developer role has been removed, users who have not been updated to use the “Manage API keys” = Allow permission will:

• Be unable to access the API keys UI in Profile > Settings
• Find their API keys disabled, resulting in 3rd-party integrations failing (Error: 401 Authorization Required)

API keys are not deleted from Qlik Cloud and will automatically be re-enabled once a user has been assigned the required Manage API Keys permissions.

To resolve this, a Tenant Administrator needs to act as outlined in What action do I need to take?

How was the deprecation communicated and what products were affected by the removal of the role and toggle?

The deprecation notice was communicated in an Administration announcement and documented on our What's New in Qlik Cloud feed. See Developer role and API key toggle deprecated | 6/16/2025 for details.

The following products were affacted:

• Qlik Cloud Analytics
• Qlik Talend Cloud

Related Information

• Developer role and Enable API keys toggle deprecated | Qlik Developer Portal
• Qlik Cloud: An error occurred when generating the ... - Qlik Community - 2534515

[sanrout]

Hi

We assigned new custom role to the users who are previously in the "Developer" role

Regards,

Shankar

[GreenLantern]

Really poor to way of implementing this change. This is a breaking change. Qlik should have created a new custom role by default if the tenant had API keys issued. 

[SivenM2020]

We are waiting for the RCA of this change.

We had multiple SaaS customers affected by this.