Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
I am trying to get a list of all paths available in the QRS API using this path:
/qrs/about/description
Help page can be found here:
List all paths available in the Qlik Sense Repository Service (QRS) API
I am connecting using .NET framework and authenticating using certificates:
I am getting the following response (WebException):
No matching endpoint found
The remote server returned an error: (404) Not Found.
I successfully managed to get data via other endpoints, for example:
/qrs/app
/qrs/stream
/qrs/license
Is the path (/qrs/about/description) still available? Did it change?
Has anyone experienced the same issue or successfully fetched a list of all the available paths in the QRS?
Bas Knol
Hi,
To get a list of endpoints using the QRS API you can use this endpoint:
/qrs/about/api/description
The word 'api' was added to the endpoint, probably to group endpoints that give information about the QRS API.
I have tested this successfully on Qlik Sense Server v1.1. In the v1.1 help the old /qrs/about/description endpoint is still mentioned.
In the v2.0.1 help this new endpoint is mentioned and also works on v1.1.
Bas Knol
Hi Bas,
Did you find an answer to your questions, because I am facing the same problems.
Thanks in advance.
Jan-Paul
Hi Jan-Paul,
I did not find an answer to this problem yet. I had this issue on Qlik Sense Server version 1.0.0.
I haven't tested if this issue persist in the latest version 1.0.2.
In the documentation you can find a list of all the endpoints:
List of all endpoints QRS API in help
Currently I keep a local copy (in my solution) of all the endpoints mentioned in the documentation, instead of fetching a list of all the endpoints through the API.
Please let me know if you find anything regarding this issue.
Bas Knol
Hey Bas,
It has been reported and logged as a bug following your thread back in 2014.
The bug has been resolved but I'm not sure if it made it into the 1.1 build or not, let me test that and get back to you.
As the API documentation is autogenerated we switched testing schema to ensure that missing endpoints does not make it into the docs again, thanks for bringing it up
Hi Bas,
Thanks for the info.
Currently I am using 1.0.2 and the issue still persists in this version.
Reading Alexander's answer, we have to wait for 1.1 or later.
Jan-Paul
Hi Alexander,
Thanks for your information.
Good to know it is reported as a bug and also has been resolved.
Please keep us posted in which build the endpoint will be available again
Bas
Hi all,
I have the same problem with v1.1, also for endpoint /qrs/app. Any idea what the problem is? How to leverage QRS API at all then?
- Ralf
Just want to add I'm using Java to access the APIs...
..if you can read docu and use POST method this works fine. 😉
Hi,
any news regarding this bug? Will the fix be included in 2.0 release? And by the way, is the date for 2.0 beta release set?
Alex