All Verbs | /channels/{Channel}/chat |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
From | query | string | No | |
ToUserId | query | string | No | |
Channel | path | string | No | |
Message | query | string | No | |
Selector | query | string | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Id | form | long | No | |
Channel | form | string | No | |
FromUserId | form | string | No | |
FromName | form | string | No | |
DisplayName | form | string | No | |
Message | form | string | No | |
UserAuthId | form | string | No | |
Private | form | bool | No |
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
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}