Discussions

While integrating Live Avatar in custom mode, I encountered an issue where multiple start session API calls return the same session ID. In a multi-user, real-time interactive avatar setup similar to HeyGen, this creates a serious conflict: when multiple users are active simultaneously and I send a command (for example, triggering speech or interrupting the avatar), the action propagates to any one of the users sharing that session ID. This breaks user isolation and causes cross-user interference.

I am looking for guidance on how session IDs are expected to behave in this mode, whether unique session IDs per user are guaranteed or require additional parameters, and what the recommended architectural approach is to ensure strict one-to-one mapping between a user and a live avatar session.