To override the Content-type in your clients, use the HTTP Accept Header, append the .soap12 suffix or ?format=soap12
HTTP + SOAP12
The following are sample HTTP requests and responses.
The placeholders shown need to be replaced with actual values.
POST /soap12 HTTP/1.1
Host: equipstage2.e-isg.com
Content-Type: text/xml; charset=utf-8
Content-Length: length
<?xml version="1.0" encoding="utf-8"?>
<soap12:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
<soap12:Body>
<CallTransientService xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/eQuipModel">
<domainDataJson>String</domainDataJson>
<tokenID>String</tokenID>
<transientDataServiceURL>String</transientDataServiceURL>
<userID>String</userID>
</CallTransientService>
</soap12:Body>
</soap12:Envelope>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<?xml version="1.0" encoding="utf-8"?>
<soap12:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
<soap12:Body>
<ResponseForTokenID xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/eQuipModel">
<TokenID>String</TokenID>
</ResponseForTokenID>
</soap12:Body>
</soap12:Envelope>