Evo Voice

<back to all web services

LiveAnswerSendEmail

The following routes are available for this service:
All Verbs/nodes/live-answer/email
import datetime
import decimal
from marshmallow.fields import *
from servicestack import *
from typing import *
from dataclasses import dataclass, field
from dataclasses_json import dataclass_json, LetterCase, Undefined, config
from enum import Enum, IntEnum


@dataclass_json(letter_case=LetterCase.CAMEL, undefined=Undefined.EXCLUDE)
@dataclass
class LiveAnswerEmailRecipient:
    name: Optional[str] = None
    address: Optional[str] = None


@dataclass_json(letter_case=LetterCase.CAMEL, undefined=Undefined.EXCLUDE)
@dataclass
class LiveAnswerSendEmail:
    flow_id: Optional[str] = None
    session_id: Optional[str] = None
    node_id: Optional[str] = None
    client_id: Optional[str] = None
    subject: Optional[str] = None
    body: Optional[str] = None
    to: Optional[List[LiveAnswerEmailRecipient]] = None
    cc: Optional[List[LiveAnswerEmailRecipient]] = None
    bcc: Optional[List[LiveAnswerEmailRecipient]] = None

Python LiveAnswerSendEmail DTOs

To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json

To embed the response in a jsonp callback, append ?callback=myCallback

HTTP + JSON

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/json
Content-Type: application/json
Content-Length: length

{"flowId":"String","sessionId":"String","nodeId":"String","clientId":"String","subject":"String","body":"String","to":[{"name":"String","address":"String"}],"cc":[{"name":"String","address":"String"}],"bcc":[{"name":"String","address":"String"}]}