Update testing-with-postman.mdx

[varunkakkar]

Corrected the Postman Example to use the GET /sessionInfo API where POST /change-user-data is being used

Summary of change

The Documentation for Testing with Postman mentions the use of a POST /change-user-data API. The said API has been updated to GET /sessionInfo but the same does not reflect in the Documentation.

The documentation also states an incorrect response message to the GET /sessionInfo API which says try refresh token instead of unauthorized

This pull request updates the documentation to reflect the same.

[netlify[bot]]

✅ Deploy Preview for admiring-bhabha-7b1be9 ready!

Name	Link
🔨 Latest commit	4060b5a20cee6bed6d39b38523d0ad62557bfe0e
🔍 Latest deploy log	https://app.netlify.com/sites/admiring-bhabha-7b1be9/deploys/6509dce261b38a0008c7d4c7
😎 Deploy Preview	https://deploy-preview-713--admiring-bhabha-7b1be9.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[rishabhpoddar]

Hey @varunkakkar

The said API has been updated to GET /sessionInfo but the same does not reflect in the Documentation.

Where has this happened?

[varunkakkar]

Hi @rishabhpoddar, I was running the backend server and testing the same with Postman for the emailpassword recipe. To do this I was following the steps in the documentation.

The documentation mentions POST /change-user-data API to verify the access token validity. Which is incorrect as the API which I could see in the backend server was GET /sessionInfo

[rishabhpoddar]

The docs also mentions that you should add the /change-user-data to the backend server. So this isn't really any issue IMO.

[rishabhpoddar]

Closing this due to no response, and cause the change is not needed.