Unable to access Status APIs | Community
Skip to main content
yashp0808
yashp0808
New Participant
February 12, 2024
Solved

Unable to access Status APIs

  • February 12, 2024
  • 3 replies
  • 769 views

Hi Team,

 

Over the past few days, we have observed that while trying to connect to Adobe Status APIs via OAuth token, we are getting error - {"error_code":"403013","message":"Your IP is not allowlisted"}. We did not have to allow any IPs earlier and were able to access the APIs successfully. Can you please let us know if there is a change in process for consuming the APIs or is there anything else that we need to do to get the valid response? Attaching screenshots for the requests being blocked.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by yashp0808

@arunpatidar thank you for sharing the documentation. I was trying to consume an Adobe API and not create a custom one. Anyway, the issue seems to be fixed now without any changes done from our end. I assume it was a temporary glitch. 

 

Thanks,

Yash

3 replies

kautuk_sahni
kautuk_sahni
Employee
February 16, 2024

@yashp0808 Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.

Kautuk Sahni
SureshDhulipudi
SureshDhulipudi
New Participant
February 13, 2024

Is there any change to you Network or IP address?

or VPN enabled vs Dynamic IP or any change network security changes?

Did you try with any Other different network ?

    arunpatidar
    arunpatidar
    New Participant
    February 12, 2024

    Hi @yashp0808 
    Could you please check https://developer.adobe.com/runtime/docs/guides/using/creating_rest_apis/ 

    Arun Patidar
      yashp0808
      yashp0808AuthorAccepted solution
      New Participant
      February 13, 2024

      @arunpatidar thank you for sharing the documentation. I was trying to consume an Adobe API and not create a custom one. Anyway, the issue seems to be fixed now without any changes done from our end. I assume it was a temporary glitch. 

       

      Thanks,

      Yash

        Terms & ConditionsAccessibility statement

        Loading footer...