Docs · 2 of 5 · about 3 minutes

Connect with the LiveKit SDK

Your signal host is a LiveKit server. Every LiveKit client SDK connects to it with the same call it uses for LiveKit Cloud, so the only thing that changes in your app is the URL.

Flutter

final room = Room();
await room.connect('wss://acme-7k2q.livecore.cloud', token);

JavaScript / React

const room = new Room();
await room.connect('wss://acme-7k2q.livecore.cloud', token);

Swift

let room = Room()
try await room.connect(url: "wss://acme-7k2q.livecore.cloud", token: token)

Kotlin

val room = LiveKit.create(applicationContext)
room.connect("wss://acme-7k2q.livecore.cloud", token)

What stays the same

Everything you do after connect(): publishing and subscribing to tracks, simulcast and adaptive stream, data channels, participant events, reconnection. We run the same open-source server LiveKit Cloud runs, so the SDK cannot tell the difference, and neither should your code.

ReferenceRoom, tracks, events and every SDK option: docs.livekit.io ↗. We do not duplicate it here on purpose — their reference is maintained by the people who write the SDKs.

What is different

The URL is yours: wss://<your-slug>-<suffix>.livecore.cloud. TLS is already in place; there is nothing to configure.
Tokens are signed with the key and secret we gave you, not a LiveKit Cloud key. Page 3.
Your rooms are yours alone. Room names are namespaced to your tenant invisibly, so a name another tenant uses never collides with yours.