Evo Voice

<back to all web services

ChatEventsNodeNewMessageCallback

The following routes are available for this service:
All Verbs/nodes/chat-events/new-message
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 ChatEventsNodeNewMessageCallback:
    account_id: Optional[str] = None
    endpoint_id: Optional[str] = None
    session_id: Optional[str] = None
    body: Optional[str] = None
    sender: Optional[str] = None
    sender_display_name: Optional[str] = None
    attachment_uri: Optional[str] = None
    attachment_content_type: Optional[str] = None
    new_message: Optional[str] = None
    new_message_body: Optional[str] = None
    new_message_sender: Optional[str] = None

Python ChatEventsNodeNewMessageCallback DTOs

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/chat-events/new-message HTTP/1.1 
Host: evovoice.io 
Accept: application/xml
Content-Type: application/xml
Content-Length: length

<ChatEventsNodeNewMessageCallback xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Voice.Api.Nodes.Messaging">
  <AccountId>String</AccountId>
  <AttachmentContentType>String</AttachmentContentType>
  <AttachmentUri>String</AttachmentUri>
  <Body>String</Body>
  <EndpointId>String</EndpointId>
  <NewMessage>String</NewMessage>
  <NewMessageBody>String</NewMessageBody>
  <NewMessageSender>String</NewMessageSender>
  <Sender>String</Sender>
  <SenderDisplayName>String</SenderDisplayName>
  <SessionId>String</SessionId>
</ChatEventsNodeNewMessageCallback>