| All Verbs | /nodes/chat-events/new-message |
|---|
using System;
using System.IO;
using System.Collections;
using System.Collections.Generic;
using System.Runtime.Serialization;
using ServiceStack;
using ServiceStack.DataAnnotations;
using Voice.Api.Nodes.Messaging;
namespace Voice.Api.Nodes.Messaging
{
public partial class ChatEventsNodeNewMessageCallback
{
public virtual string AccountId { get; set; }
public virtual string EndpointId { get; set; }
public virtual string SessionId { get; set; }
public virtual string Body { get; set; }
public virtual string Sender { get; set; }
public virtual string SenderDisplayName { get; set; }
public virtual string AttachmentUri { get; set; }
public virtual string AttachmentContentType { get; set; }
public virtual string NewMessage { get; set; }
public virtual string NewMessageBody { get; set; }
public virtual string NewMessageSender { get; set; }
}
}
C# ChatEventsNodeNewMessageCallback DTOs
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: team.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>