topic Re: Problem reading reload status through PI in Integration, Extension & APIs

Problem reading reload status through PI

claudio_pette — Wed, 11 Feb 2026 11:07:10 GMT

Hi everyone, I'm having a problem setting up a new user (which Splunk will use) to monitor the status of reload tasks.
I'm using QS on Windows (2024).

I created a dedicated user (splunk_sv), and I created security rules in reads for ReloadTask_*, ExecutionSession_*, and ExecutionResult_*, but Splunk can't query the qrs/reloadtask APIs, giving a connection error.

I haven't assigned any licenses.

Is this configuration correct?

Re: Problem reading reload status through PI

erin77brown — Thu, 12 Feb 2026 04:31:13 GMT

Your configuration is mostly on the right track, but the likely culprit is that Qlik Sense requires an allocated license (Professional or Analyzer) for a user to interact with the QRS API, even for service accounts. Without a license, the user is essentially "anonymous" to the system and will be blocked from API endpoints. Additionally, ensure your security rule specifically grants the "Read" and "Access" actions and that the splunk_sv user is correctly identified by their UserDirectory and UserId. Finally, verify that your Splunk connection is including the necessary X-Qlik-Xrfkey header and the correct client certificate to avoid handshake or connection errors service finance login

Re: Problem reading reload status through PI

rwunderlich — Wed, 11 Feb 2026 16:50:52 GMT

"Qlik Sense requires an allocated license (Professional or Analyzer) for a user to interact with the QRS API"

That is an incorrect statement. QRS API does not require a license.

Can you post any more detail on the connection error?

-Rob

Re: Problem reading reload status through PI

Levi_Turner — Wed, 11 Feb 2026 19:48:27 GMT

Example Query being made:

GET /qrs/reloadtask/full?xrfkey=NTI0MTUwNjA0MzUy
X-Qlik-XrfKey: NTI0MTUwNjA0MzUy
X-Qlik-User: UserDirectory=splunk; UserId=demo
Accept: application/json
Content-Type: application/json
Host: <my_server>:4242

Example Security Rule:

The result operates as expected (all reload tasks, no external program tasks or user directory synchronization tasks).