| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| query | string | Yes | ||
| password | query | string | Yes | |
| webyn | query | string | Yes | |
| iosyn | query | string | Yes | |
| devicetoken | query | string | Yes | |
| appversion | query | string | No | |
| versioncode | query | string | No | |
| token3ds | query | string | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .soap12 suffix or ?format=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: ssl.buildersaccess.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>
<login xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/BASchedulingSDK">
<appversion>String</appversion>
<devicetoken>String</devicetoken>
<email>String</email>
<iosyn>String</iosyn>
<password>String</password>
<token3ds>String</token3ds>
<versioncode>String</versioncode>
<webyn>String</webyn>
</login>
</soap12:Body>
</soap12:Envelope>