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: ssl.buildersaccess.com
Content-Type: text/xml; charset=utf-8
Content-Length: length
SOAPAction: sch_SaveFinalIntroWalkSignV2022
<?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>
<sch_SaveFinalIntroWalkSignV2022 xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/BASchedulingSDK">
<idintrowalksign>String</idintrowalksign>
<page10_b1>String</page10_b1>
<page10_b1_i1>String</page10_b1_i1>
<page10_b1_i10>String</page10_b1_i10>
<page10_b1_i11>String</page10_b1_i11>
<page10_b1_i2>String</page10_b1_i2>
<page10_b1_i3>String</page10_b1_i3>
<page10_b1_i4>String</page10_b1_i4>
<page10_b1_i5>String</page10_b1_i5>
<page10_b1_i6>String</page10_b1_i6>
<page10_b1_i7>String</page10_b1_i7>
<page10_b1_i8>String</page10_b1_i8>
<page10_b1_i9>String</page10_b1_i9>
<page10_b2>String</page10_b2>
<page11_b1>String</page11_b1>
<page11_b2>String</page11_b2>
<page13_b1>String</page13_b1>
<page13_b2>String</page13_b2>
<page14_b1>String</page14_b1>
<page14_b2>String</page14_b2>
<page15_b1>String</page15_b1>
<page15_b2>String</page15_b2>
<page16_b1>String</page16_b1>
<page16_b2>String</page16_b2>
<page16_pm>String</page16_pm>
<page17_b1>String</page17_b1>
<page17_b2>String</page17_b2>
<page17_pm>String</page17_pm>
<page4_2_b1>String</page4_2_b1>
<page4_2_b2>String</page4_2_b2>
<page5_b1_initial>String</page5_b1_initial>
<page6_b1>String</page6_b1>
<page6_b2>String</page6_b2>
<page8_b1>String</page8_b1>
<page8_b2>String</page8_b2>
<page9_b1>String</page9_b1>
<page9_b2>String</page9_b2>
<puchlist xmlns:d2p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays">
<d2p1:string>String</d2p1:string>
</puchlist>
<token>String</token>
<tokensecret>String</tokensecret>
<page12_b1_initial>String</page12_b1_initial>
<page18_b1>String</page18_b1>
<page18_b2>String</page18_b2>
<V2022>String</V2022>
</sch_SaveFinalIntroWalkSignV2022>
</soap:Body>
</soap:Envelope>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<?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>
<AppResponse.Sch_Returndata xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/BASchedulingSDK">
<_x003C_found_x003E_k__BackingField>String</_x003C_found_x003E_k__BackingField>
<_x003C_message_x003E_k__BackingField>String</_x003C_message_x003E_k__BackingField>
<_x003C_validtoken_x003E_k__BackingField>String</_x003C_validtoken_x003E_k__BackingField>
</AppResponse.Sch_Returndata>
</soap:Body>
</soap:Envelope>