topic Re: QRS API call in Integration, Extension & APIs

QRS API call

uridiumabs — Wed, 15 Feb 2017 14:10:02 GMT

Hi,

I'm trying to make a QRS API call using postman. Acording to the documentation i do the following:

GET -> https://{server}/qrs/app/full?Xrfkey=abcdefghijklmnoq‌‌

and adding headers as suggested:

X-Qlik-Xrfkey = abcdefghijklmnoq

X-Qlik-User = UserDirectory=INTERNAL; UserId=sa_repository

I'm getting a 401 error (Unauthorized)

If I add a User-Agent Header i can get a 200 - OK return code but i'm receiving an html login screen asking for user an password.

I'm using Qlik Sense 3.1 and the link i'm following is:

Connecting with Postman ‒ Qlik Sense

Has anybody be successful with this and can explain where is the error?. I try with windows authentication. Actually what i want is to start a task but would like to know what I'm doing wrong.

Thanks.

Re: QRS API call

Anonymous — Tue, 28 Feb 2017 22:32:52 GMT

Hi Juan, it looks like it should work, is that a valid login for the QMC in normal circumstances? Have you also exported the certificate (you should get a warning in postman if the cert is invalid).

In postman, I have the following:

GET Request

URL: https://<server URL>:4242/qrs/app/full?xrfkey=0123456789abcdef

two headers:

X-Qlik-xrfkey

0123456789abcdef

X-Qlik-User

UserDirectory=<my domain>;UserId=<my username> (my user is a rootadmin in QMC, but I don't think it should matter as long as the user can login and do the same task in QMC)

Re: QRS API call

grangerats — Tue, 28 Feb 2017 22:50:10 GMT

You don't mention that you have client-certificates setup properly and working. Without that, you cannot access the QRS API. Everything else seems fine, unless you're not using port 4242.

Re: QRS API call

uridiumabs — Fri, 03 Mar 2017 15:53:43 GMT

Hi,

You both are right. I didn't use the certificates not port 4242.

Thank you very much