Skip to main content
SDKs are how your product opens a session. The server still does the ingest, the process, and the deliver. The SDK gets a person publishing or playing. Browser publish and play can also speak WHIP and WHEP directly when you want that protocol in the open. The SDK is the path when the session should feel like part of your product. Package names and method references belong on this page once they match the release you ship. Use the packages that arrive with the license, and keep the REST API as the source for creating the stream and rotating keys.