| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| token | query | string | No | |
| tokensecret | query | string | No | |
| idcia | query | string | No | |
| idvendor | query | string | No | |
| masteridcia | query | string | No | |
| keyword | query | string | No | |
| page | query | string | No | |
| datefrom | query | string | No | |
| dateto | query | string | No | |
| targetidcia | query | string | No | |
| status | query | List<string> | No | |
| lasttitle | query | string | No |
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: sch_home
<?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>
<sch_home xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/BASchedulingSDK">
<datefrom>String</datefrom>
<dateto>String</dateto>
<idcia>String</idcia>
<idvendor>String</idvendor>
<keyword>String</keyword>
<lasttitle>String</lasttitle>
<masteridcia>String</masteridcia>
<page>String</page>
<status xmlns:d2p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays">
<d2p1:string>String</d2p1:string>
</status>
<targetidcia>String</targetidcia>
<token>String</token>
<tokensecret>String</tokensecret>
</sch_home>
</soap:Body>
</soap:Envelope>