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

00024962: QRS API

generalfinance — Fri, 18 Feb 2022 11:21:46 GMT

Hi Joseph,

Excuse me if to write again, but now that I understand how it work postman, I'd like extract all task in failed.
I see that you can filter by state in this case I am interested at the status Failed which corresponds to number 8, but at the same time I would like to filter by task and have the task id with description.
What kind of get or post should I do?
I found this guide
https://help.qlik.com/en-US/sense-developer/November2021/APIs/RepositoryServiceAPI/index.html?page=1030

Thank you for support

Re: 00024962: QRS API

Øystein_Kolsrud — Fri, 18 Feb 2022 12:17:34 GMT

The endpoint you are pointing to is probably what you want. If you only want the tasks that have latest execution result "Finished Failed", then you should filter that endpoint on that. Like this:

GET /qrs/reloadtask?filter=operational.lastExecutionResult.status eq 8

The full list of enumeration values to use for that status property can be found here:

https://help.qlik.com/en-US/sense-developer/February2022/APIs/RepositoryServiceAPI/index.html?page=1829

Re: 00024962: QRS API

generalfinance — Fri, 18 Feb 2022 13:18:49 GMT

Thanks so much for the support, that was just what I was interested in getting.

Have a nice day

Marco

Re: 00024962: QRS API

generalfinance — Thu, 03 Mar 2022 16:35:01 GMT

Hi Joseph,

With postman I get the response correct in format json, but I would like get the same thing with monitoring system PRTG Passler, but I have this error, you have idea if is possible do or if someone has already done so?

A thousand thanks.

Re: 00024962: QRS API

generalfinance — Thu, 17 Mar 2022 09:59:35 GMT

Hi, thanks for support, if you a wanted a check a specific task in this case i know the id for example bdcc21ec-265e-4e6c-9883-c60443fb4f22, How can i do?
I tried with this string but it doesn't work

GET 7qrs/reloadtask/"bdcc21ec-265e-4e6c-9883-c60443fb4f22"?filter=operational.lastExecutionResult.status eq 8&Xrfkey=***************

Another question, is there another way to get without postman but using a browser?

Thank you.

Re: 00024962: QRS API

Øystein_Kolsrud — Thu, 17 Mar 2022 14:36:51 GMT

You can call GET requests by just typing the endpoint in the browser, but you'll need to add a xrfkey. The same value needs to be provided both in a header and as part of the URL:

https://help.qlik.com/en-US/sense-developer/February2022/Subsystems/RepositoryServiceAPI/Content/Sense_RepositoryServiceAPI/RepositoryServiceAPI-Connect-API-Using-Xrfkey-Headers.htm

So if you are already logged in (just go to the hub or qmc) and add the header "X-Qlik-Xrfkey" with value "0123456789abcdef", then you can call endpoints like this:

https://<server>/qrs/about?xrfkey=0123456789abcdef

You'll probably need some plugin to set the header though. Here's an example:

https://chrome.google.com/webstore/detail/modheader/idgpnmonknjnojddfkpgkljpfnnfcklj

But this approach only allow you to call GET endpoints.

Re: 00024962: QRS API

generalfinance — Fri, 18 Mar 2022 16:58:54 GMT

HI,

I was able to test the same call with the browser and with ModHeader, but in this case I'm doing filtering all the tasks that are in fail, if I just wanted to filter a specific task what is the correct syntax?
Another thing I didn't understand every task must have its own X-Qlik-Xrfkey? If so, how can I recover it?

https://server:4242/qrs/reloadtask?filter=operational.lastExecutionResult.status%20eq%208&Xrfkey=012345789abcdef

Thanks for the support.

Re: 00024962: QRS API

Øystein_Kolsrud — Mon, 21 Mar 2022 10:28:56 GMT

Filtering on id is the typical thing to do if you want a specific task. Something like this:

GET /qrs/reloadtask?filter=id eq <id>

Or simply like this:

GET /qrs/reloadtask/<id>

Re: 00024962: QRS API

generalfinance — Mon, 21 Mar 2022 11:38:42 GMT

Hi,

I built the get as follows:

https: //server: 4242 /qrs /reloadtask / "bdcc21ec-265e-4e6c-9883-c60443fb4f22 & Xrfkey" = 012345789abbcdef

but I get

XSRF prevention check failed. Possible XSRF discovered.

Could it be that by directly calling a specific id, the correct Xrfkey must be found?

Thank you

Re: 00024962: QRS API

Øystein_Kolsrud — Mon, 21 Mar 2022 11:46:28 GMT

You shouldn't have the quotes in the url. It should look like this:

https://server: 4242/qrs/reloadtask/bdcc21ec-265e-4e6c-9883-c60443fb4f22?Xrfkey=012345789abbcdef

Re: 00024962: QRS API

Øystein_Kolsrud — Mon, 21 Mar 2022 11:47:32 GMT

And you had a double 'b' in your xrfkey. Might have been a typo, but it probably shouldn't be there.

Re: 00024962: QRS API

stefanstoichev123 — Mon, 21 Mar 2022 12:05:32 GMT

Also ... the same Xrfkey should be passed as a header - X-Qlik-Xrfkey.

In your case the url is https://server:4242/qrs/reloadtask/bdcc21ec-265e-4e6c-9883-c60443fb4f22?Xrfkey=012345789abbcdef

and there should be a header X-Qlik-Xrfkey with value 012345789abbcde (exactly the same as Xrfkey value in the url param)

More about Xrfkey can be found at the "Using Xrfkey headers" documentation section