React
iOS
Android
Flutter
Angular
JavaScript
Unity
Unreal
Node
Python
Ruby
PHP
Java
.NET
Go
RESTServer-Side Overview
Parts of Stream Chat are configured from your backend rather than from a client SDK. App settings, permissions, webhooks, push templates, data retention and campaigns are all set up with a server-side SDK or the REST API, authenticated with your API secret. That code never runs in your app.
Those pages used to appear in this sidebar. They now live in the server-side documentation, so the pages here stay focused on the code you ship to your users.
What you will find there
| Section | Covers |
|---|---|
| App and channel settings | App-wide settings, roles and permission policies, per-channel setting overwrites |
| Webhooks | Event delivery, SQS, SNS and failover; chat keeps the event catalogue and message hooks |
| Push configuration | Notification templates; providers, devices and preferences moved to the platform push pages |
| Campaigns | Sending a message to a segment of your users |
| Server-driven messaging | AI message streaming, unread reminders, restricted message delivery |
| Channel lookup | Fetching one channel by type and ID without creating it |
| Data and compliance | Retention policies, audit logs, GDPR deletion, exporting and importing channels |
| Migration | Moving an existing app onto Stream |
| Scale and operations | Dynamic partitioning, user average response time, Datadog integration |
| Plan limits | Fair usage allowances, storage and bandwidth |
| Marketplace apps | Two-sided marketplace patterns built on channel type configuration |
Languages
The server-side docs are published per language. Pick yours from the selector at the top of the page: Node.js, Python, Go, Java, Ruby, PHP or C#.
If you landed here because your client cannot connect, token generation is the usual cause. Tokens must be signed with your API secret on your server, so a client SDK cannot mint one. Start with Authentication and tokens.