QRS API using Connecting with Postman / Qlik Sense 3.0

[#1]

Hell Everyone

I tried Qlik help page Qlik_Sense_Repository_Service_API‌ to query the QRS API but to no avail. I use the certificate as a trusted method of authentication as well as the X-Qlik-User header

I flowed this tutorial to setup my Virtual proxy https://github.com/stefanwalther/articles/blob/master/header-authentication-configuration/readme.md

Also followed Qlik online help to set up the proxy, I am using Postman

My URL in postman: https://localhost:4242/hdr/qrs/app?Xrfkey=12345678qwertyui

Also tried https://qlikserver1:4242/hdr/qrs/app?Xrfkey=12345678qwertyui

Where qlikserver1 is the host machine name, also tried changing the order of hdr and qrs

I added the X-Qlik-xrfkey then tried with and without X-Qlik-User in the header, after many tested and combinations, each time I either get resource not found or user not permitted to make such API call or end point not found...

Can someone share his/her experience if they managed to make such QRS API. It will be nice to share the Virtual proxy settings and a simple call using Postman.

Many thanks

//Youness

[#2 · Accepted solution]

I solved it

This is the correct link structure it seems to me the online help file hasn't been updated, there is no need for port number 4242.

https://qlikserver1/qrs/About?Xrfkey=12345678qwertyui

There is no need to create a new virtual proxy as used to be in the past

Make sure to enable "Interceptor" in Postman, it is another extension you will have to install.

I got this answer back from the QRS API

{"buildVersion":"2.2.4.0","buildDate":"9/20/2013 10:09:00 AM","databaseProvider":"Devart.Data.PostgreSql","nodeType":1,"schemaPath":"About"}

Cheers

// Youness

[santhyamuthu]

Hi Youness,

Do you have an explanation as to how the API responded with Postman interceptor turned on? I had to do the same to test my APIs but did not quite understand what difference does this make for the requests?

Without Interceptor it kept giving me "401 unauthorized" message

Thanks,

Santhya