Skip to main content
Woohoo! Qlik Community has won “Best in Class Community” in the 2024 Khoros Kudos awards!
Announcements
Nov. 20th, Qlik Insider - Lakehouses: Driving the Future of Data & AI - PICK A SESSION
cancel
Showing results for 
Search instead for 
Did you mean: 
NZFei
Partner - Specialist
Partner - Specialist

Qlik REST Connector Request Body format is not right

Hi Guys,

I am trying to POST to an API endpoint TrackUnit to have the token using Qlik REST connector and I had the following error.  After doing some tests (for example inputting the wrong user name and pw on purpose), I figured out that the format to embed multiple lines into request body is not accepted by the API end point. 

I used the same credentials and could POST successfully in Postman but in Qlik REST connector, it returned and said invalid credentials:

 

NZFei_0-1699423268021.png

 

Does anyone know how to fix this? The format grant_type=password&username=xxx&password=xxx in request body does not work. What should be the correct format?

 

Thanks a lot!

 

Fei

 

Labels (3)
5 Replies
stefanstoichev123

Im not familiar with TrackUnit specifics but can see from their documentation that the body for the "token" request should be in "x-www-form-urlencoded" format. 

Could you please try and add query header to your request "Content-Type" with value "application/x-www-form-urlencoded" and then try again?

Stefan

NZFei
Partner - Specialist
Partner - Specialist
Author

Thank you for your reply. I already added that to the header.

yanela-somdaka
Partner - Contributor II
Partner - Contributor II

Hi NZFei,

Did you manage to resolve this issue? I am also dealing with a very similar issue.
Thanks

NZFei
Partner - Specialist
Partner - Specialist
Author

No, my client has given up.

It is not the only time that you can make API work in Postman but not Qlik REST connector...

yanela-somdaka
Partner - Contributor II
Partner - Contributor II

My client also 'gave up' and is exploring other options. In their case, it would seem that the API development did not adhere to API standards.