<back to all web services
LiveAnswerSendEmail
The following routes are available for this service:| All Verbs | /nodes/live-answer/email | | |
|---|
LiveAnswerSendEmail Parameters:| Name | Parameter | Data Type | Required | Description |
|---|
| FlowId | query | string | No | |
| SessionId | query | string | No | |
| NodeId | query | string | No | |
| ClientId | query | string | No | |
| Subject | query | string | No | |
| Body | query | string | No | |
| To | query | List<LiveAnswerEmailRecipient> | No | |
| Cc | query | List<LiveAnswerEmailRecipient> | No | |
| Bcc | query | List<LiveAnswerEmailRecipient> | No | |
LiveAnswerEmailRecipient Parameters:| Name | Parameter | Data Type | Required | Description |
|---|
| Name | form | string | No | |
| Address | form | string | No | |
To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml
HTTP + XML
The following are sample HTTP requests and responses.
The placeholders shown need to be replaced with actual values.
POST /nodes/live-answer/email HTTP/1.1
Host: evovoice.io
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<LiveAnswerSendEmail xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Voice.Api.Nodes.AI">
<Bcc>
<LiveAnswerEmailRecipient>
<Address>String</Address>
<Name>String</Name>
</LiveAnswerEmailRecipient>
</Bcc>
<Body>String</Body>
<Cc>
<LiveAnswerEmailRecipient>
<Address>String</Address>
<Name>String</Name>
</LiveAnswerEmailRecipient>
</Cc>
<ClientId>String</ClientId>
<FlowId>String</FlowId>
<NodeId>String</NodeId>
<SessionId>String</SessionId>
<Subject>String</Subject>
<To>
<LiveAnswerEmailRecipient>
<Address>String</Address>
<Name>String</Name>
</LiveAnswerEmailRecipient>
</To>
</LiveAnswerSendEmail>