| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| token | query | string | Yes | |
| tokensecret | query | string | Yes | |
| pmname | query | string | Yes | |
| idwebcare1 | query | string | Yes | |
| idwebcare1detail2 | query | string | Yes | |
| scheduledate | query | string | Yes | |
| schedulebesttime | query | string | Yes | |
| scheduleconfirm | query | string | Yes |
To override the Content-type in your clients, use the HTTP Accept Header, append the .soap11 suffix or ?format=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: ba_schedulepm
<?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>
<ba_schedulepm xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/BASchedulingSDK">
<idwebcare1>String</idwebcare1>
<idwebcare1detail2>String</idwebcare1detail2>
<pmname>String</pmname>
<schedulebesttime>String</schedulebesttime>
<scheduleconfirm>String</scheduleconfirm>
<scheduledate>String</scheduledate>
<token>String</token>
<tokensecret>String</tokensecret>
</ba_schedulepm>
</soap:Body>
</soap:Envelope>