App settings for export with API

[luke_brady]

While i've been using the Qlik developer API here: https://qlik.dev/apis/

I've noticed there are some apps where an export is not possible. After looking at the json of an app that could be exported:

"privileges":["read","update","delete","reload","export","duplicate","change_owner","change_space","export_reduced","source","exportappdata"]

and comparing this to an app where an exception was thrown when trying to export:

"privileges":["read","delete","change_owner","export_reduced"]

It's clear the app where an export is possible has a lot more privileges, including "export". What I'm hoping someone can explain to me is what determines if an app can be exported or not? I presume this is some sort of setting that can be controlled, but it's not immediately clear to me where this would be found.

Does anyone have an answer to this or have an idea how one could have a look at the different settings?

Thank you in advance.

[marksouzacosta]

I believe an app can be exported or not based on the user rights on that app and/or space.

[luke_brady]

@marksouzacosta 

Thank you for your reply.

Looking at some apps and spaces where I don't have the possibility to export them, I'm still able to open the app and delete, which is consistent with the privileges here:

"privileges":["read","delete","change_owner","export_reduced"

Looking in the management console however, I can't see anywhere, even as an admin, that these rights can be changed or added to.

I can't imagine that the creator of one of these apps has purposely removed or prevented certain permissions being given when it was created, so I'm trying to find a connection somewhere as to how these privileges can be looked at more closely.

[luke_brady]

Okay, so after talking to the Qlik support via live chat, it seems that you user who's API Key is trying to export either needs the rights "to edit" or "to manage" on the space itself that these privileges are given.

[marksouzacosta]

Yes, that is true. The API Key represents the user that own's the key. So, it must have access to everything that you are touching in Qlik, like Automations, Data Connections, Spaces, Apps with Section Access, etc.