Skip to main content

Applying a license to Qlik DataMarket

Before you can use Qlik DataMarket data, you must accept the terms and conditions for its use. Also, if you have bought a license for premium data packages, you must enter your access credentials to use data in those packages. You can access some DataMarket data without a license. Some data is restricted, however, and requires a license. The data that requires a license is marked Premium in the selection dialogs. Once access credentials have been applied, the premium data is labeled Licensed.

Information noteIt is not necessary to accept Qlik DataMarket terms and conditions when using Qlik Sense Desktop. Access credentials are also not required because the premium data sets are not available on Qlik Sense Desktop.

Do the following:

  1. Open the Qlik Management Console.
  2. Select Qlik DataMarket under License and tokens.
  3. Select I accept the terms and conditions.
  4. Select a Subscription, either Free or Licensed subscription.

  5. If you select the Licensed subscription, enter your access credentials:

    Owner name

    Owner organization

    Serial number

    Control number

  6. After entering your access credentials, expand LEF access and click Get LEF and preview the license to download an LEF file from the Qlik SenseLEFserver.

    Information noteFailed to get LEF from server is displayed if the serial number or control number is incorrect.

    If your installation site has restricted Internet access, you will not be able reach the Qlik license server. In that case, you can copy the LEF information from an LEF file and paste it in the text field. Your Qlik representative can provide the license file.

    Information noteIf you have restricted Internet access, you will also not be able to reach the Qlik DataMarket server to select data. To gain access, you must add the Qlik DataMarket domain to a white-list of allowable domains. The DataMarketdomain is datamarket-api.qlik.com.
  7. Click Apply.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!