| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| token | query | string | Yes | |
| tokensecret | query | string | Yes | |
| query | string | Yes | ||
| name | query | string | No | |
| phone | query | string | No | |
| homePhone | query | string | No | |
| address | query | string | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| result | form | int | No | |
| message | form | 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>
<post_profile xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/BASchedulingSDK.post.login">
<address>String</address>
<email>String</email>
<homePhone>String</homePhone>
<name>String</name>
<phone>String</phone>
<token>String</token>
<tokensecret>String</tokensecret>
</post_profile>
</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>
<post_profileResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/BASchedulingSDK.post.login">
<message>String</message>
<result>0</result>
</post_profileResponse>
</soap12:Body>
</soap12:Envelope>