Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik and ServiceNow Partner to Bring Trusted Enterprise Context into AI-Powered Workflows. Learn More!
cancel
Showing results for 
Search instead for 
Did you mean: 
SayanCiti007
Contributor II
Contributor II

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

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.

Labels (4)
9 Replies
kallnascimento
Partner - Contributor III
Partner - Contributor III

Hello @SayanCiti007,

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

rwunderlich
Partner Ambassador/MVP
Partner Ambassador/MVP

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

Levi_Turner
Employee
Employee

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.

jeffersonshibuya
Partner - Contributor III
Partner - Contributor III

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"
}
SayanCiti007
Contributor II
Contributor II
Author

SCRIPTSCRIPTLOGLOG

SayanCiti007
Contributor II
Contributor II
Author

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

SayanCiti007
Contributor II
Contributor II
Author

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,

kallnascimento
Partner - Contributor III
Partner - Contributor III

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

rwunderlich
Partner Ambassador/MVP
Partner Ambassador/MVP

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

-Rob