React
iOS
Android
Flutter
Angular
JavaScript
Unity
Unreal
Node
Python
Ruby
PHP
Java
.NET
Go
RESTClient-Side Overview
Parts of Stream Chat only exist in your app. A server client authenticates with your API secret and makes ordinary HTTP calls, so it has no connected user and no WebSocket. Anything built on those two things belongs in a client SDK.
Those pages used to appear in this sidebar. They now live in the client SDK documentation, so the pages here stay focused on code you can actually run on a server.
What moved
| Page | Covers |
|---|---|
| Initialization & Users | Creating a client from the API key alone, connectUser, token providers, disconnecting |
| Authless Users | Guest and anonymous sessions, which need no server-side authentication |
| Typing Indicators | keystroke, stopTyping, and the typing.start event |
| User Presence | Watching channels with presence: true, online state and last_active |
The Polls API page moved for the same reason: its examples are written for JavaScript, Kotlin, Swift, Dart and Unity. It stays in the Node sidebar, because stream-chat is the same package a Node server uses.
The presence fields themselves are still documented here, under Managing Users and Query Members.
Client SDKs
The pages above are linked to the JavaScript docs, which is where the redirects point. Each client SDK documents the same features in its own language:
One thing does not move. The token your app connects with must be signed with your API secret, so it is minted here, on your server. See Tokens & Authentication.