Forum Discussion

dilawar's avatar
dilawar
Occasional Contributor
3 years ago

The API works fine on ReadyAPI, but on the website, the API doesn't work properly

I hope you're doing well. I have successfully implemented SOAP XML in ReadyAPI, and it's functioning properly. However, I'm encountering an issue with Postman. This problem might be related to header...
integrations
SOAP
KarelHusa's avatar
KarelHusa
Super Contributor
3 years ago

dilawar,

you need to make sure you fill the HTTP headers as expected by your server-side:

  • Content-Type: specifying the type of data you send within the request body
  • SOAPAction: the operation identification

 

An example is:

Content-Type: text/xml;charset=UTF-8
SOAPAction: "http://tempuri.org/IConnectPoint_Reservation/GetReservationsByNationalId"

 

The API tools may fill these headers differently, e.g. Postman using "application/xml" instead of "text/xml". ReadyAPI made the best job to match to your API here.

 

  • dilawar's avatar
    dilawar
    Occasional Contributor
    3 years ago

     

    SOAPAction: http://tempuri.org/IConnectPoint_Reservation/CreatePNR
    Content-Type: text/xml;charset=UTF-8


    I'm passing this soap action and content-type if National id is issue so why this is working on ready api  but postman and SwaggerHub Explore issues facing.