Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
adam_westhusing
Contributor II
Contributor II

Is it possible to export extensions via QRS API?

From the UI you can export extensions in the QMC.  Is it possible to export extensions via the QRS API or another Qlik Sense API? !

1 Solution

Accepted Solutions
Levi_Turner
Employee
Employee

Hey Adam,

Sure. The endpoint is going to be GET https://servername:443/api/wes/v1/extensions/export/ExtensionName

In a Qlik CLI framework the code would be like this:

# Scrape the hostname from the Host.cfg

$Data = Get-Content C:\ProgramData\Qlik\Sense\Host.cfg

# Convert the base64 encoded install name for Sense to UTF data

$FQDN = [System.Text.Encoding]::UTF8.GetString([System.Convert]::FromBase64String($($Data)))

Connect-Qlik -ComputerName https://$($FQDN):443 -UseDefaultCredentials

Invoke-QlikDownload -path https://$($FQDN)/api/wes/v1/extensions/export/blah -filename blah.zip

View solution in original post

4 Replies
Levi_Turner
Employee
Employee

Hey Adam,

Sure. The endpoint is going to be GET https://servername:443/api/wes/v1/extensions/export/ExtensionName

In a Qlik CLI framework the code would be like this:

# Scrape the hostname from the Host.cfg

$Data = Get-Content C:\ProgramData\Qlik\Sense\Host.cfg

# Convert the base64 encoded install name for Sense to UTF data

$FQDN = [System.Text.Encoding]::UTF8.GetString([System.Convert]::FromBase64String($($Data)))

Connect-Qlik -ComputerName https://$($FQDN):443 -UseDefaultCredentials

Invoke-QlikDownload -path https://$($FQDN)/api/wes/v1/extensions/export/blah -filename blah.zip

adam_westhusing
Contributor II
Contributor II
Author

This worked perfectly for me.  Thanks!

adam_westhusing
Contributor II
Contributor II
Author

@Levi_TurnerIs this API documented somewhere in the Qlik Documentation?  I'm curious if I can get a list of endpoints similar to calling GET /qrs/about/api/description?extended=true

Aiham_Azmeh
Employee
Employee

Hi,
This API is not part of the repository API (QRS) and not documented since it's a private API.
But, if you are curious, you should be able to access the specs through `/api/wes/v1/openapi`