| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| token | query | string | Yes | |
| tokensecret | query | string | Yes | |
| idcia | query | string | Yes | |
| pmname | query | string | Yes | |
| idwebcare1 | query | string | Yes | |
| emailto | query | string | Yes | |
| emailcc | query | string | Yes | |
| subject | query | string | Yes | |
| notes | query | string | Yes | |
| ack | query | string | Yes | |
| emailtoname | query | string | Yes | |
| callflag | query | int | No | |
| idvendor | query | int | No | |
| validyn | query | int | 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: ba_sendemailpm
<?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_sendemailpm xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/BASchedulingSDK">
<ack>String</ack>
<callflag>0</callflag>
<emailcc>String</emailcc>
<emailto>String</emailto>
<emailtoname>String</emailtoname>
<idcia>String</idcia>
<idvendor>0</idvendor>
<idwebcare1>String</idwebcare1>
<notes>String</notes>
<pmname>String</pmname>
<subject>String</subject>
<token>String</token>
<tokensecret>String</tokensecret>
<validyn>0</validyn>
</ba_sendemailpm>
</soap:Body>
</soap:Envelope>