topic Re: 🔔 Upcoming removal of GET method for /api/v1/apps in Qlik Cloud Analytics, May 2026 in App Development

🔔 Upcoming removal of GET method for /api/v1/apps in Qlik Cloud Analytics, May 2026

Daniele_Purrone — Tue, 21 Apr 2026 13:50:32 GMT

Previously, the /api/v1/apps endpoint could be used to list all apps on a tenant. This method has always been unsupported and undocumented, and will be removed in the first week of May 2026.

Check this blog post for all the details.

Re: 🔔 Upcoming removal of GET method for /api/v1/apps in Qlik Cloud Analytics, May 2026

F_B — Tue, 28 Apr 2026 13:23:25 GMT

Somehow I missed the detail blog link before, thank you Daniele for adding it

Re: 🔔 Upcoming removal of GET method for /api/v1/apps in Qlik Cloud Analytics, May 2026

Daniele_Purrone — Wed, 06 May 2026 08:47:15 GMT

This is now deployed in all regions.

Re: 🔔 Upcoming removal of GET method for /api/v1/apps in Qlik Cloud Analytics, May 2026

Sunilsahu_345 — Fri, 22 May 2026 09:11:06 GMT

Thanks for confirming the rollout, Daniele — this is a really important change to highlight.

For anyone who was (knowingly or unknowingly) relying on the /api/v1/apps GET endpoint, it’s definitely worth reviewing your integrations now. Since it was undocumented, I’ve seen a few internal tools and scripts still using it for quick app listings, especially in automation or governance checks.

From what I understand, the recommended approach going forward is to rely on supported APIs like:

The Items API (/api/v1/items) for listing apps with more structured metadata
Or leveraging spaces + app relationships via the Spaces API, depending on how your tenant is organized

One thing to watch out for is pagination and filtering behavior, which differs slightly compared to the old endpoint. If you had scripts assuming a flat list of apps, you may need to adjust logic to handle:

Resource types (app, sheet, etc.)
Space context (shared, managed, personal)
Access control differences

Also, for larger tenants, it’s a good opportunity to revisit performance and rate limits when switching to supported endpoints, especially if you're running scheduled jobs.

If anyone is migrating existing scripts, I’d recommend testing with:

Service account/API key access
Scoped queries (instead of pulling everything at once)
Proper error handling for permission-based responses