To override the Content-type in your clients, use the HTTP Accept Header, append the .soap11 suffix or ?format=soap11
HTTP + SOAP11
The following are sample HTTP requests and responses.
The placeholders shown need to be replaced with actual values.
POST /soap11 HTTP/1.1
Host: equipstage3.e-isg.com
Content-Type: text/xml; charset=utf-8
Content-Length: length
SOAPAction: GetAssetReservationCalendar
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<GetAssetReservationCalendar xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/eQuipModel">
<IsAssetReservationData>false</IsAssetReservationData>
<IsReservationData>false</IsReservationData>
<IsResourceData>false</IsResourceData>
<SearchCriteriaCollection xmlns:d2p1="http://schemas.datacontract.org/2004/07/eQuip.Domain.Reservation">
<d2p1:SearchParam>
<d2p1:FieldName>String</d2p1:FieldName>
<d2p1:FieldValue />
<d2p1:Operator>String</d2p1:Operator>
</d2p1:SearchParam>
</SearchCriteriaCollection>
<UserID>String</UserID>
</GetAssetReservationCalendar>
</soap:Body>
</soap:Envelope>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
(string)