GET operation works in Postman but not in SailPoint

Hello All,

I am getting below error which doing test connection operation with GET API call. The same works in Postman and I’m able to get the output. Not sure why its throwing 400 error which is bad request. This is GET operation and I’m not passing anything in the body.

Only “authorization” and “host” are the two headers required for this operation

Hi @JackSparrow Without further info on your config, hard to diagnose. Basically, for a GET, a 400 is saying the URL or the headers are malformed.

@JackSparrow

just use 2** in success codes and try

Hi @j_place , Below are the setting defined. Same works in POSTMAN



Hi @sidharth_tarlapally , Tries adding 2** in error codes, still its failing

@JackSparrow

Remove 200 just place 2** only one

Thanks @JackSparrow What Authentication type are you using?

What is your BaseURL in your config? Did you already include a
“/” at the end of your base URL? If so, you don’t need the / before ‘fusion’ in your context URL

@sidharth_tarlapally still the same error
@j_place we are using custom authtentication
@margocbain Base URL doesn’t have “/”

Actually, the same GET request is working as expected in Postman. I used POST method instead of GET for test connection and that is working as expected.

Authorization is the only header that I’m passing, rest are calculated by Postman. Even I tried adding these headers in SailPoint, but no luck.

@JackSparrow

What is the response code that you are seeing in postman is it 200 ?

Thats correct. Its 200

Hi. Do you have any parameters in the base URL?

Hi @j_place , No we don’t have any query/path parameters

Hello,

Change your Request Type to Curl and paste the curl generated in postman and see if the error message change.

Shot in the dark - Could you try without the paginationRequired query parameter?

Hi @JackSparrow ,

This issue typically occurs due to the authentication type. Please try using a different authentication type.

Hey all,

Test connection is working with POST request where I am calling token generation end point. Now when I try to call any of GET request by manually updating the token in the headers, its throwing me 400 error, so issue is not with authentication. This is something else.

I have raised a case and asked for logs as its SaaS based connector. Will keep posted here.