Evo Voice

<back to all web services

ChatEventsNodeNewMessageCallback

The following routes are available for this service:
All Verbs/nodes/chat-events/new-message
"use strict";
export class ChatEventsNodeNewMessageCallback {
    /** @param {{accountId?:string,endpointId?:string,sessionId?:string,body?:string,sender?:string,senderDisplayName?:string,attachmentUri?:string,attachmentContentType?:string,newMessage?:string,newMessageBody?:string,newMessageSender?:string}} [init] */
    constructor(init) { Object.assign(this, init) }
    /** @type {string} */
    accountId;
    /** @type {string} */
    endpointId;
    /** @type {string} */
    sessionId;
    /** @type {string} */
    body;
    /** @type {string} */
    sender;
    /** @type {string} */
    senderDisplayName;
    /** @type {string} */
    attachmentUri;
    /** @type {string} */
    attachmentContentType;
    /** @type {string} */
    newMessage;
    /** @type {string} */
    newMessageBody;
    /** @type {string} */
    newMessageSender;
}

JavaScript ChatEventsNodeNewMessageCallback DTOs

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

HTTP + OTHER

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: text/jsonl
Content-Type: text/jsonl
Content-Length: length

{"accountId":"String","endpointId":"String","sessionId":"String","body":"String","sender":"String","senderDisplayName":"String","attachmentUri":"String","attachmentContentType":"String","newMessage":"String","newMessageBody":"String","newMessageSender":"String"}