Hi Experts,
We have a requirement from our current customer where they are providing us a SOAP WS.For one of the method we are passing“username” & “password” as input parameters and getting one security key (some unique number) in the response. We are able to do OData modeling for the same method. So far, it is fine.
For other method, we have to pass that ”security key” in header along with some other parameters in the body section. While doing the request mapping for this method, we don’t see any option for this key parameter apart from those parameters (in that body section).
We found one publicly available WSDL to reproduce the same scenario:
- e.g http://api.geosvc.com/services/soap?wsdl . To access its one of the method/operationGetPlace,We have to pass APiKey and Cursor value in the header section.
<wsdl:message name="GetPlaceRq_Headers">
<wsdl:part name="ApiKey" element="tns:ApiKey"/>
<wsdl:part name="Cursor" element="tns:Cursor"/>
To get APiKey, we have to register first.http://www.geosvc.com/register , once its done, you will get one APiKey as below:
The same API keyhas to pass to access “GetPlace” method. So we tried it in SOAP UI to understand how exactly it should work:
As you can see below, for the method “GetPlace”, we are passing values as in:
Header Value | |
Cursor | blank |
ApiKey | df7f8cc90e3345b4980cf6631f33a32d |
Body | |
Country | US |
Place | HOLLYWOOD,CA |
Also got the response.
When we do modeling (more precisely request mapping as below) for the same method we don’t see any Header related parameters. We can see only parameters which are available in the BODY section.
We thought if we can get APIKey parameter in the body sections only, then it would be easy to map with. Right?
What do you suggest how we should handle this kind of scenarios?
CC: Mustafa Saglam, Jeff Gebo, Bjoern Woppmann
Regards,
JK