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

Announcements
Join us to spark ideas for how to put the latest capabilities into action. Register here!
cancel
Showing results for 
Search instead for 
Did you mean: 
mstoler
Partner - Specialist
Partner - Specialist

curl commands with Qlik SAAS`

Hello,

Has anyone been successful in getting the qlik saas api to work using curl.

I am using this command:

curl  -L -H 'authorization: bearer <your-api-key>' \
  https://your-tenant.us.qlikcloud.com/api/v1/items?limit=2&resourceType=app

But get the error 401 authorization required.

Thanks,

Michael

1 Solution

Accepted Solutions
Levi_Turner
Employee
Employee

I am finding success with:

curl  -L -H 'Authorization: Bearer <your-api-key>' \
  https://your-tenant.us.qlikcloud.com/api/v1/items

on my Linux Subsystem for Windows install and success with

curl  -L -H "Authorization: Bearer <your-api-key>" \
  https://your-tenant.us.qlikcloud.com/api/v1/items

with my curl for Windows (https://curl.se/windows/) launched through cmd.exe install.

I suspect your problem is casing. Authorization vs. authorization and Bearer vs. bearer.

View solution in original post

3 Replies
Damien_V
Support
Support

Hello @mstoler 

Is this still an issue ? Looking in our logs, it looks you were able to authenticate.

If the issue is solved please mark the answer with Accept as Solution.
mstoler
Partner - Specialist
Partner - Specialist
Author

Hello,

Yes still an issue.  

I just submitted some curl commands today. Please let me know what you see.

 

Thank You,

 

Michael

Levi_Turner
Employee
Employee

I am finding success with:

curl  -L -H 'Authorization: Bearer <your-api-key>' \
  https://your-tenant.us.qlikcloud.com/api/v1/items

on my Linux Subsystem for Windows install and success with

curl  -L -H "Authorization: Bearer <your-api-key>" \
  https://your-tenant.us.qlikcloud.com/api/v1/items

with my curl for Windows (https://curl.se/windows/) launched through cmd.exe install.

I suspect your problem is casing. Authorization vs. authorization and Bearer vs. bearer.