topic Re: Call to QRS API giving error "404 Not Found" error and the message "No matching endpoint found". in Connectivity & Data Prep

Call to QRS API giving error "404 Not Found" error and the message "No matching endpoint found".

SayanCiti007 — Thu, 23 Apr 2026 11:50:05 GMT

objective : Need to fetch all qvs for all apps in the server to get the lineage details.

We are attempting to run a PowerShell script as a QMC External Program Task to call the QRS API. ( Also tried from the server ) The script successfully authenticates and can list all apps via /qrs/app/full. However, any attempt to get details for a single app (e.g., /qrs/app/{id}/script or /qrs/app/{id}) fails with a "404 Not Found" error and the message "No matching endpoint found".

We have confirmed the following:

The service user has RootAdmin privileges.
The certificate is correct and loads successfully.
The API calls work correctly when run from a standard PowerShell window on the same server, but fail when run via a QMC task.
The issue persists even with a minimal, hardcoded script, ruling out script logic errors.

Re: Call to QRS API giving error "404 Not Found" error and the message "No matching endpoint found".

kallnascimento — Thu, 23 Apr 2026 12:20:24 GMT

Hello @SayanCiti007,

I'd recommend you use dev-hub or Butler-Spyglass.

Re: Call to QRS API giving error "404 Not Found" error and the message "No matching endpoint found".

rwunderlich — Thu, 23 Apr 2026 14:23:07 GMT

My guess is that your {id} parm is getting messed up. Anything that doesn't look like the expected 36 character guid pattern will return the 404. Can you print out the full url in your script before you send it to debug?

-Rob

Re: Call to QRS API giving error "404 Not Found" error and the message "No matching endpoint found".

Levi_Turner — Thu, 23 Apr 2026 17:22:55 GMT

Definitely check the other suggestions but I did want to point out that /qrs/app/{id}/script doesn't exist.

Some snippet of script may help to see what may be the cause but if you get a result from the full endpoint (app/full) or the condensed endpoint (app), then I would not expect an app specific (app/id) to fail.

Re: Call to QRS API giving error "404 Not Found" error and the message "No matching endpoint found".

jeffersonshibuya — Thu, 23 Apr 2026 17:38:49 GMT

try add this header explicitly to every request:

$headers = @{
"X-Qlik-Xrfkey" = "0123456789abcdef"
"X-Qlik-User" = "UserDirectory=INTERNAL; UserId=sa_api"
"Content-Type" = "application/json"
}

Re: Call to QRS API giving error "404 Not Found" error and the message "No matching endpoint found".

SayanCiti007 — Fri, 24 Apr 2026 06:59:06 GMT

SCRIPTLOG

Re: Call to QRS API giving error "404 Not Found" error and the message "No matching endpoint found".

SayanCiti007 — Fri, 24 Apr 2026 07:01:12 GMT

using dev hub we cant export script at bulk for 100 apps.

Re: Call to QRS API giving error "404 Not Found" error and the message "No matching endpoint found".

SayanCiti007 — Fri, 24 Apr 2026 10:00:30 GMT

It seems to be error is happening only on script end point . the other QRS API call is successfull. I tried with object fetch and it worked.

$objectsUrl = "$qrsServer/qrs/app/object/full?xrfkey=$xrfkey&filter=$encodedFilter"

/qrs/app/{id}/script endpoint.- this is not working seems to be,

Re: Call to QRS API giving error "404 Not Found" error and the message "No matching endpoint found".

kallnascimento — Fri, 24 Apr 2026 11:39:46 GMT

Using butler spyglass, you can extract data connections, lineage e app scripts from all your apps.

Re: Call to QRS API giving error "404 Not Found" error and the message "No matching endpoint found".

rwunderlich — Fri, 24 Apr 2026 14:08:14 GMT

As @Levi_Turner pointed out, /script is not a valid endpoint for QRS.

-Rob