Server-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

Every page that moved is listed here so you can go straight to it.

SectionPages
App and channel settingsApp Settings, Channel Types, User Permissions, Channel Setting Overwrites
WebhooksEvents, Before Message Send Webhook, Custom Commands Webhook. Delivery, SQS, SNS and failover are on the platform webhooks pages
Push configurationCustomizing Notifications, Legacy Push System. Providers, devices and preferences are on the platform push pages
Server-driven messagingAI Message Streaming, Unread Reminders, Campaign API
Channel lookupGetting a Channel
Data and complianceAudit Logs, Data Retention Policy, Importing Data, Exporting Data
MigrationMigration Guide
Scale and operationsDynamic Partitioning, User Average Response Time, Datadog Integration
Plan limitsFair Usage Limits, Storage and Bandwidth
Marketplace appsMarketplace Apps

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.

Previous
Reference
Next
Rate Limits