Bot
Subscription (Web socket)
Overview
Our GraphQL subscription endpoint:
1
wss://api-ws.dlive.tv
Copied!
Note that, the subscription does not work like normal GraphQL subscription in the sense that it returns every possible event with all available fields regardless of the subscription query given. So you cannot only listen to, say chat messages, and so you need to filter out uninterested events.
The server sends a "ka" message every 25 seconds. If you do not receive "ka", you should reconnect.
Endpoints
We currently provide two web socket endpoints type. One for livestream/chat events
streamMessageReceived and the other for chest events treasureChestMessageReceived .The currently available
streamMessageReceived events are:Event
Description
Message
Chat message
Gift
Donation
Live
Stream go live
Offline
Stream go offline
Follow
First time follow
Subscription
Subscribe
Delete
Message deletion
Host
Host
ChatMode
Change of chat mode
Ban
User banned
Mod
Moderator add/remove
Emote
Emote addition
Timeout
User timeout
The currently available
treasureChestMessageReceived events are:Event
Description
TreasureChestGiveawayEnded
Chest giveway ended message
TreasureChestGiveawayStarted
Chest giveway started message. Chest value should be updated to 0.
TreasureChestValueExpired
Some amount of chest value is expired message
TreasureChestValueUpdated
Chest value updated message
How to connect
Clients establish a secure WebSocket connection to our endpoint.
Client sends
1
{
2
"type": "connection_init",
3
"payload": {
4
"authorization" : "YOUR_APP_ACCESS_TOKEN"
5
}
6
}
Copied!
and expects to receive an ack:
1
{
2
"type":"connection_ack"
3
}
Copied!
Then client could subscribe to a particular endpoint by sending as follows:
1
{
2
"id":"1",
3
"type":"start",
4
"payload":{
5
"query":"subscription{streamMessageReceived(streamer:\"dbl-lee\"){__typename}}"
6
}
7
}
Copied!
The id is a unique string during current connection and "dbl-lee" is the
username of the streamer (NOT displayname).When a chat message is received, you should receive:
1
{
2
"payload":{
3
"data":{
4
"streamMessageReceived":[
5
{
6
"__typename":"ChatText",
7
"type":"Message",
8
"id":"80364c42-1d4e-49f2-ac16-dffc9cb2e3d8",
9
"content":"hello",
10
"createdAt":"1560812097380375004",
11
"sender":{
12
"__typename":"StreamchatUser",
13
"id":"streamchatuser:testpotato",
14
"username":"testpotato",
15
"displayname":"testPotato",
16
"avatar":"https://images.prd.dlivecdn.com/avatar/default22.png",
17
"partnerStatus":"NONE",
18
"badges":[]
19
},
20
"role":"None",
21
"roomRole":"Member",
22
"subscribing":false
23
}
24
]
25
}
26
},
27
"id":"1",
28
"type":"data"
29
}
Copied!
You could subscribe to multiple streamers and distinguish server payload by the
id string. The schema of different events could be found by clicking corresponding types here.Note that, sending message is not through web socket but by mutation.
To unsubscribe to a particular endpoint, just send stop message with id as follows:
1
{
2
"id":"1",
3
"type":"stop"
4
}
Copied!
Last modified 2yr ago
Copy link