| All Verbs | /nodes/chat-events/new-message | 
|---|
| Name | Parameter | Data Type | Required | Description | 
|---|---|---|---|---|
| AccountId | query | string | No | |
| EndpointId | query | string | No | |
| SessionId | query | string | No | |
| Body | query | string | No | |
| Sender | query | string | No | |
| SenderDisplayName | query | string | No | |
| AttachmentUri | query | string | No | |
| AttachmentContentType | query | string | No | |
| NewMessage | query | string | No | |
| NewMessageBody | query | string | No | |
| NewMessageSender | query | string | 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 /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>