Watching a Channel

The call to channel.watch does a few different things in one API call:

  • It creates the channel if it doesn’t exist yet (if this user has the right permissions to create a channel)

  • It queries the channel state and returns members, watchers and messages

  • It watches the channel state and tells the server that you want to receive events when anything in this channel changes

To start watching a channel

The examples below show how to watch a channel. Note that you need to be connected as a user before you can watch a channel.

const state = await channel.watch();

Response Schema

NameTypeDescription
configobjectThe configuration for the channel type.
channelobjectThe Channel object.
onlineintegerNumber of online members.
watchersobjectUsers that are watching this channel. Represented as a mapping from the user id to the user object.
membersobjectChannel members. Represented as a mapping from the user id to the user object.
readobjectRead messages grouped by user id. Represented as a mapping from the user id to the message object.

Watching a channel only works if you have connected as a user to the chat API

Watchers vs Members

The concepts of watchers vs members can require a bit of clarification:

  • members : a permanent association between a user and a channel. If the user is online and not watching the channel they will receive a notification event, if they are offline they will receive a push notification.

  • watchers : the list of watchers is temporary. It’s anyone who is currently watching the channel.

Being able to send messages, and otherwise engage with a channel as a non-member requires certain permissions. For example, we have pre-configured permissions on our livestream channel type to allow non-members to interact, but in the messaging channel type, only members of the channel can interact.

Watching Multiple Channels

The default queryChannels API returns channels and starts watching them. There is no need to also use channel.watch on the channels returned from queryChannels

// first let’s create a filter to make messaging channels that include a specific user
const filter = { type: "messaging", members: { $in: [user_id] } };
// we can also define a sort order of most recent messages first
const sort = { last_message_at: -1 };

// finally, we can query for those channels, automatically watching them for the
// currently connected user
const channels = await client.queryChannels(filter, sort, { watch: true });

Stop Watching a Channel

To stop receiving channel events:

// we can also stop watching a channel
const stopWatching = await channel.stopWatching();

Watcher Count

To get the watcher count of a channel:

// filter on a specific channel cid
const filter = { cid: channelCID };
// sort by most recent messages first
const sort = { last_message_at: -1 };

// retrieve our channels
const channels = await client.queryChannels(filter, sort);

// each channel object has a state collection with a watcher_count property
return channels[0].state.watcher_count;

Paginating Channel Watchers with channel.query

// create a new channel of type “livestream” with name “watch-this-channel”
const channel = client.channel("livestream", "watch-this-channel", {});

// now query the newly created channel for watchers, retrieving the first 5
const result = await channel.query({
  watchers: { limit: 5, offset: 0 },
});

return result.watchers;

The maximum limit that can be used is 300, and the maximum offset that can be used is 10 000.

Listening to Changes in Watchers

A user already watching the channel can listen to users starting and stopping watching the channel with the realtime events:

const channel = client.channel("livestream", "watch-this-channel", {});

channel.watch();

channel.on("user.watching.start", (event) => {
  // handle watch started event
  console.log(`${event.user.id} started watching`);
});
channel.on("user.watching.stop", (event) => {
  // handle watch stopped event
  console.log(`${event.user.id} stopped watching`);
});
© Getstream.io, Inc. All Rights Reserved.