Server-Side Overview

Parts of Stream Video are configured from your backend rather than from a client SDK. Call types, recording, transcription, webhooks and SIP 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 have moved to the server-side documentation, which has its own section, so the pages here stay focused on the code you ship to your users.

What the server-side docs cover

Section	Covers
Users and tokens	Creating users, generating the tokens your client connects with
Call types	Defaults, permissions, geofencing and settings that apply to every call of a type
Streaming	Backstage, RTMP, WHIP and SRT ingress, HLS output
Recording	Composite, individual track, raw and frame recording, plus storage
Transcription	Transcriptions, captions and where they are stored
SIP	Inbound trunks, DTMF, Twilio and Telnyx integrations
Webhooks	Event delivery, SQS and SNS; the event catalogue stays here
Quality	Latency, networking and firewall rules, connection tests, stats
Analytics	Call attendance, participant metrics, user feedback
Asynchronous operations	Monitoring the long-running tasks that return a task ID
Rate limits	Per-endpoint video limits; shared mechanics live on the platform page
Moderation	Audio and video moderation
GDPR and privacy	Exporting and deleting user data, plus deleting calls

Languages

Every server-side page has code tabs for Node.js, Python, Go, Java and cURL. Pick your backend language at the top of each example.

Note:

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. Start with Users and tokens.