Skip to main content

Hi all, I’m running into a strange issue with a REST API endpoint.

When I hit the endpoint in the browser (while logged in), I get the expected JSON data. But when I try the same request in Postman or via a script, I get a 200 OK response with an empty body.

Endpoint->
https://hostname.com/main/ifsapplications/projection/v1/RecruitmentRequisitionHandling.svc/PersonnelRequisitions 

Postman Response

 

Browser Response

Troubleshooting so far:

  • Confirmed authentication is working (token/session returns 200).

  • Exported and replicated browser headers (including auth cookies/token) in Postman.

  • Behavior persists across network environments and users.


Has anyone else faced this kind of issue? If so, what was the root cause or workaround that helped you resolve it?

I tried linking the user I created to the company and site that this projection’s results belongs to as suggested by this link, but still the result is empty.

Hi,

Just checking (I know you said it persists across users) but are you using the same username within Postman as you logged in with when you used the browser?

MMck

 

Hi ​@MMcK, nope.

I used IFSAPP user account, and another user account. The account I am using on Postman  is an IAM_USER I created and assigned rights and access to this projection.

Hi VICMUMO

Try using the same account in Postman as you used for the browser.  I believe there are additional rules for users about what HR information they can access.

 

Hi ​@MMcK, the postman request uses OAuth2.0, I provide a client_id + secret key. I don’t think the user+password applies in this case.

As well as the client id and key you also provide user information in Postman

The username and password needs to be the same as you’ve used for the browser, so that the rules for accessing the HR data are applied consistently.

 

Thank you, ​@MMcK.

Your suggestion completely did the trick—it was the missing piece I’d been chasing for hours. The data is now flowing as expected in Postman.

Really appreciate you sharing your insight.

Reply


Terms & ConditionsCookie settings