| All Verbs | /ba_sendemailvendor |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| token | query | string | Yes | |
| tokensecret | query | string | Yes | |
| idcia | query | string | Yes | |
| idvendor | 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 | |
| validyn | query | int | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /xml/oneway/ba_sendemailvendor HTTP/1.1
Host: ssl.buildersaccess.com
Content-Type: application/xml
Content-Length: length
<ba_sendemailvendor 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>String</idvendor>
<idwebcare1>String</idwebcare1>
<notes>String</notes>
<subject>String</subject>
<token>String</token>
<tokensecret>String</tokensecret>
<validyn>0</validyn>
</ba_sendemailvendor>