جارٍ التحميل...
01 · Choose your path
No matter your level. Every path leads to a working production integration.
02 · Quickstart · 5 minutes
Sign up → copy your key → paste one line. We explain every line below.
Free plan, no credit card. From the console you get a public key (pk_live_…) for browsers and a secret key (sk_live_…) for your server. Treat sk_ like a database password.
On every page render, your server signs the visitor's identity (email + name) with sk_, POSTs it to /api/public/v1/sdk-token, and gets back a 1-hour browser-safe JWT. This is what the browser uses.
Add a <script> tag with your pk_ and the JWT. The floating call/chat bubble appears. Wire your existing button to LIQAA.startCall(...). Done.
Stuck? Full quickstart docs · partners@tkawen.com
03 · By framework
12 official guides. Native SDKs for the popular ones, plain HTTP for the rest.
Hooks + components via @liqaa/react
App Router + RSC compatible
Composition API plugin
One <script> tag, zero install
Server-side token signing
curl + hash_hmac, full example
requests + hmac, drop-in
net/http + crypto/hmac
Official plugin, point-and-click
Liquid snippet + app proxy
Server SDK examples
iOS + Android via WebView
04 · By use case
Every recipe ships with a working code sample, a screenshot of the result, and the trade-offs we'd pick.
See it · Live
The bubble appears the moment the SDK loads. A user clicks. Within milliseconds, a signed JWT is exchanged, ICE candidates negotiate, and a WebRTC peer connection forms. Encrypted, end to end.
05 · Core concepts
No prior video infrastructure experience required. We explain everything from scratch.
A browser standard for real-time audio/video. The peer-to-peer protocol Google Meet, Discord, and you (now) use. We handle the hard parts: signaling, NAT traversal, simulcast.
pk_live_… is your public key — safe to ship to browsers. sk_live_… is your secret key — server-only. Same pattern as Stripe. We refuse any browser request that uses sk_.
On every page load, your server signs the user's identity with sk_, exchanges it for a 1-hour browser-safe JWT. The JWT is room-scoped and time-bounded.
Same user pair = same room across calls. No new room ID per call cluttering your dashboard. Idempotent by external_conversation_id.
We POST events to your URL, signed with HMAC-SHA256. You verify the signature, reject replays older than 5 min. No "did this come from LIQAA?" guesswork.
For 2 peers, P2P is fine. For 3+, you need a Selective Forwarding Unit (SFU) so each peer sends video once instead of N times. We run LiveKit SFU globally.
06 · Under the hood
Your site speaks HTTPS+JWT to LIQAA Cloud. LIQAA negotiates a WebRTC session with the LiveKit SFU. Media flows directly. We never touch the bytes.
07 · Going live
Before you flip pk_test_ to pk_live_, walk through these.