Forum Discussion

smynam's avatar
smynam
New Contributor
5 years ago

API Works on Postman- Imported Request to Ready API Doesnt work

Hi  My API woks in Postman it is a simple get request, under authorization tab passing in credentials [username & password] and default headers -  In Readyapi imported the collection through the in...
  • smynam's avatar
    smynam
    5 years ago

    This is how we solved the issue. the request which we are passing through is going through Akamai gateway. 

    The Akamai has allowed the request coming from Postman as valid request, while the same request content when requested from Ready API - here Akamai flagged it as an Anomaly library [chat bot] and blocked the request which is making it to fail. 

     

    Resolution : The team has proposed adding an user-agent header in the preferences setting under http and that did the trick

     

    Please mark it as an solution once validated - happy to learn and contribute back!!

richie's avatar
richie
Community Hero

Hey @smynam 

 

so you changed the POST to a GET and now rather than 405 you're getting a 400 bad request?

 

OK - so you're getting through the auth and the content of the request itself is being treated as malformed.

 

This is a GET, right - and you haven't got a payload I'm assuming - so I'd suggest looking at the URI you are submitting.  Compare the URI you are submitting (via the RAW request details) and compare with your requirements.

I expect they'll be some mismatch - there may be a problem with your headers (you can get headers that are too long that cause a 400), but it's more likely that theres a problem with your REST parameters in the URI you are submitting.  Double check what you are submitting (via the RAW) against your requirements - you should see the problem

 

ta

 

rich

smynam's avatar
smynam
New Contributor
5 years ago

This is how we solved the issue. the request which we are passing through is going through Akamai gateway. 

The Akamai has allowed the request coming from Postman as valid request, while the same request content when requested from Ready API - here Akamai flagged it as an Anomaly library [chat bot] and blocked the request which is making it to fail. 

 

Resolution : The team has proposed adding an user-agent header in the preferences setting under http and that did the trick

 

Please mark it as an solution once validated - happy to learn and contribute back!!