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: post_tenant
<?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>
<post_tenant xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/BASchedulingSDK.post.login">
<email>String</email>
<token>String</token>
<tokensecret>String</tokensecret>
</post_tenant>
</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>
<post_tenantResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/BASchedulingSDK.post.login">
<list>
<tenantInfo>
<account>String</account>
<idcia>String</idcia>
<idnumber>String</idnumber>
<idproject>String</idproject>
<premiseAddress>String</premiseAddress>
<tenantaddress>String</tenantaddress>
<tenantcity>String</tenantcity>
<tenantname>String</tenantname>
<tenantphone>String</tenantphone>
<tenantzipcode>String</tenantzipcode>
<ticketCount>String</ticketCount>
<ticketOndoingCount>String</ticketOndoingCount>
</tenantInfo>
</list>
<message>String</message>
<result>0</result>
</post_tenantResponse>
</soap:Body>
</soap:Envelope>