Skip to main content
Starting a broadcast has two parts: the social.plus SDK returns room broadcaster credentials, and your app-owned media stack uses those credentials to connect and publish audio/video. Keep those responsibilities separate in your implementation and docs.
This page covers SDK room broadcasting APIs. Camera, microphone, LiveKit client setup, permissions, and media publishing UI are app-owned concerns after the SDK returns broadcaster data.

Platform Surface

Parameters

Lifecycle Parameters

Get Broadcaster Data

Call this after the room exists and before connecting your app-owned media client. Co-host rooms use coHostUrl and coHostToken; direct-streaming rooms use directStreamUrl.

Hand Credentials to Your Media Client

The SDK does not publish camera or microphone tracks. Use the returned URL/token with your media client, then let that client own connection, preview, mute, retry, and device-selection behavior.

Observe Broadcast Lifecycle

Use lifecycle updates to keep host UI, viewer entry points, and moderation tools aligned with the room status.

Stop the Broadcast

Stop the room when the host ends the session. Disconnect your media client separately, then call the SDK stop API so social.plus room state and viewer surfaces can move out of the live state.
Stopping a room ends the current broadcast session. Do not build a “restart the same room” flow unless your product and backend contract explicitly support it.

Media Boundary

Create Room

Create the room before fetching broadcaster credentials.

Co-Host Management

Invite, observe, and manage co-hosts before or during the broadcast.

Live Viewing

Show viewers how to watch active room broadcasts.