Qlik Cloud API to Download Reload Log file

[pipertexts]

Hi,

We are using Qlik Cloud managed spaces to publish production apps and our developers (who only have manage and edit access in Shared spaces) need the autonomy to download reload logs in case of a reload failure. However, we do not want to grant them direct access (ie "Can Manage" or "Can Edit") to these logs within the managed space because that level of access will also give them permission to reload apps, etc.

The other API endpoints we tried from the dev portal only gives us the Reload Summary but that is not sufficient for the devs.

We are exploring other options, such as downloading the logs via an API call, but we are facing an issue with the following endpoint provided by Qlik Chat support: https://<your-tenant-URL>/api/v1/apps/{appId}/reloads/logs

This endpoint does not seem to work. When we try to call it, we receive a 404 error. Does anyone have any suggestions for how to enable developers to download these logs without giving them access to the reload logs directly in the managed space (does Qlik even have this as an API feature)? Is there an alternative API or a different approach we can use to achieve this?

Any help would be greatly appreciated!

[Øystein_Kolsrud]

Can you paste the code you use? A 404 indicates that there is something wrong in the way you are calling the endpoint. I have used that one myself and it worked fine. Some spelling mistake maybe? Perhaps you have the wrong app ID?

[pipertexts]

Hi @Øystein_Kolsrud 

Good day!

This is how I called it.

Method: GET

Request endpoint: https://org-name.ap.qlikcloud.com/api/v1/apps/7a9d75f9-ea20-4b33-a93e-6c5c3b27acd8/reloads/logs

Where:

host server: https://org-name.ap.qlikcloud.com ("org-name" here is just an alias hostname just to show the format I used)

App ID: 7a9d75f9-ea20-4b33-a93e-6c5c3b27acd8

For authorization, I am using an API key that is tied to a user with admin access so should be no problem with that.

Thank you so much for responding!

[pipertexts]

Hi @Øystein_Kolsrud - sorry for the confusion. Yes, you are correct, the endpoint does work. After re-checking the request, it seems like it was a mistake from my end, there was a typo in the id. I appreciate your response!