403 Forbidden error when running API custom action in AJO

Question

Hi there,

We are trying to send a signal over to a 3rd party app to delivery SMS. There are two primary steps: 1) Fetching an OAuth Token, setting the client id and secret, and then putting the token into the Header as part of the API call, this call works in Postman.

But when I replicate the same settings into AJO, i get a 403 Forbidden error. Is there anything special I need to configure on the AJO in addition? Things I can confirm:

1) The endpoint is the same between Postman and AJO

2) Authentication returns "Test successful", and I also have this "tokenInResponse": "json://access_token" in the payload

3) The Payload request is directly copied from Postman.

Any advices would be appreciated. Thank you!!

akwankl · Accepted Answer

Thanks all. Issue happened to be with my company's own gateway config. It is resolved now!

SatheeskannaK · Answer

@akwankl It should work when it's working on the postman. Can you check for any additional headers you need to include as part of the custom action by comparing the headers that you have on the postman for the same API endpoint?

Sign up

Login with SSO

Login to the community

Login with SSO