FAQ

​

Do I need to build a video-conferencing interface?

No. LiveKit’s VideoConference component provides the standard conference layout, controls, screen sharing, and chat. The Digital Human SDK focuses on session access and digital-human-specific composition.

​

Can I show only the digital human?

Yes. Render DigitalHumanVideo without a local participant tile. The user’s camera and microphone can remain published to the room.

​

Can I call the Digital Human API directly from the browser?

No. The API key is a long-lived server credential. Use your own authenticated server route and return only a short-lived SessionConnection.

​

Can I configure the API URL?

Yes. The server client defaults to the production URL and accepts an optional absolute baseUrl. The SDK does not expose environment names.

​

Does closing the browser end the session?

Not necessarily. Call endSession from your server when your application knows the experience is complete.

​

Can the package work without React?

Yes. Use digital-human/server for session management and connect with the standard LiveKit client for your UI framework. The /react entry is optional.

​

Where should participant tokens be stored?

Prefer short-lived in-memory state. Do not put tokens in URLs, persistent browser storage, analytics events, or logs.