401 Error while decoding to JSON but 200 with postman

Help Community
,
1

hi everyone I got issue with http request
I checked the code with postman and it return code 200 and information normally
I send Post request to get token successfully then send use it for GET request
but I received the code: “401 Error while decoding to JSON” instead of 200
please take a look my setup

image
image992×879 67.1 KB

2

Hey,
Could you share JSON body request ? Please remember in UiPath to use double “” between values. Like that:

 ""body"": {
    ""ids"": [""someMessageId""]
 }
3

Hi @demon2801 ,

As per the screenshot i observed that you are using bearer token authentication for your GET request in POSTMAN so it is working fine i guess. But in UiPath http request you are using Oauth2 as authentication type that is not correct.

Please follow the same steps in http request activity as you followed in postman. refer the below steps for implementing the same in http activity in UiPath.

Use http request and Select Request Method as GET and Authorization set None like below.

image
image982×694 19.7 KB

once you select ok and go to the properties section of http request activity you could find that Headers property there click three dots and add your Bearer token (output received from your POST activity before this call) like below. please try make GET call like suggested and let us know. thanks.

image
image1692×480 30.6 KB

4

Hi all,
I have had the token by sent POST request
but after get successfully I can’t send other request with the token
I tried several times but it still failed
I think I got issue with the header
Anyone knows how to get the request header, body?

5

Another guy here with same problem.

I’m doing just like your screenshots, passing Bearer token trhough Headers, adding the "Bearer " prefix, but still and got 401. Postman works fine and returns status 200 for the very same URL and token. It seems that a lot of people is experimenting this issue…

EDIT: Just found a solution.
Check POSTMAN headers and try recreating them in the Options=>Headers property of the Http Request activity.

In my case, I think that the server side needed the Content-Type (not enough with the BodyFormat property):

imagen
imagen694×218 11.8 KB

Added the Content-Type header, and it solved the issue. Now I’m getting status 200.