| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| token | query | string | No | |
| tokensecret | query | string | No | |
| idwebcare1 | query | string | No | |
| idbsw | query | string | No | |
| repair1 | query | string | No | |
| repair2 | query | string | No | |
| repair3 | query | string | No | |
| repair4 | query | string | No | |
| repair5 | 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>
<ba_sendBSWtoHO xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/BASchedulingSDK">
<idbsw>String</idbsw>
<idwebcare1>String</idwebcare1>
<repair1>String</repair1>
<repair2>String</repair2>
<repair3>String</repair3>
<repair4>String</repair4>
<repair5>String</repair5>
<token>String</token>
<tokensecret>String</tokensecret>
</ba_sendBSWtoHO>
</soap12:Body>
</soap12:Envelope>