Getting 403 error for outbound rest message

meg6
Kilo Expert

Hi All,

I have created rest message for endpoint https://support-sp.apple.com/sp/product?cc=GVC8 , getting Method failed: (/sp/product) with code: 403 - Forbidden username/password combo error . 

and it doesn't have authentication.

Same setup is working in personal developer instance. am I missing anything?

 

Thank you

Megha BH

5 REPLIES 5

Ankur Bawiskar
Tera Patron
Tera Patron

Hi Megha,

Error 403 means you are trying to access something which is not accessible.

Can you check with the 3rd party team whether you are using correct authentication details.

Mark Correct if this solves your issue and also hit Like and Helpful if you find my response worthy based on the impact.
Thanks
Ankur

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

Hi Ankur,

Thank you for the reply.

I have tried the same API in My personal dev instance which is working fine . But its not working in the Paid dev instance.

This API will work without authentication. 

Hi Megha,

I think that API must have been registered with your demo instance and hence it may be possible that the API is not working from any other instance.

Example: The API knows that request will come from your demo instance since it must be configured that way; but since you are consuming it via paid dev instance it is not working.

Did you approach some body from the API team on how to consume the API?

Did they configure your demo instance in their side.

Mark Correct if this solves your issue and also hit Like and Helpful if you find my response worthy based on the impact.
Thanks
Ankur

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

API is open and we can access it with no authentication. We didn't configure anything in the personal dev instance, It seems like there is nothing to do in API side as it is working fine in all other instances and in postman.

This API works fine sometimes (Hardly) in paid dev instance. Not sure what the issue is.