Test

<back to all web services

PostChatToChannel

The following routes are available for this service:
All Verbs/channels/{Channel}/chat
"use strict";
export class ChatMessage {
    /** @param {{id?:number,channel?:string,fromUserId?:string,fromName?:string,displayName?:string,message?:string,userAuthId?:string,private?:boolean}} [init] */
    constructor(init) { Object.assign(this, init) }
    /** @type {number} */
    id;
    /** @type {string} */
    channel;
    /** @type {string} */
    fromUserId;
    /** @type {string} */
    fromName;
    /** @type {string} */
    displayName;
    /** @type {string} */
    message;
    /** @type {string} */
    userAuthId;
    /** @type {boolean} */
    private;
}
export class PostChatToChannel {
    /** @param {{from?:string,toUserId?:string,channel?:string,message?:string,selector?:string}} [init] */
    constructor(init) { Object.assign(this, init) }
    /** @type {string} */
    from;
    /** @type {string} */
    toUserId;
    /** @type {string} */
    channel;
    /** @type {string} */
    message;
    /** @type {string} */
    selector;
}

JavaScript PostChatToChannel 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 /channels/{Channel}/chat HTTP/1.1 
Host: test.servicestack.net 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"from":"String","toUserId":"String","channel":"String","message":"String","selector":"String"}

HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"id":0,"channel":"String","fromUserId":"String","fromName":"String","displayName":"String","message":"String","userAuthId":"String","private":false}