LiveAvatar vs HeyGen Interactive Avatar

Key differences between the two platforms

Session initialization

HeyGen required three sequential API calls: Create Session Token → New Session → Start Session.

LiveAvatar simplifies this to two calls: Create Session Token → Start Session. The old token creation and session setup logic are unified.

Session management

HeyGen	LiveAvatar
Close Session	Stop Session
Keep Alive	Keep Session Alive
List Sessions (Active)	List Sessions (type parameter)
List Sessions (History)	List Sessions (type parameter)

Task endpoints → Events

HeyGen’s REST task endpoints are replaced by an event-driven architecture:

HeyGen endpoint	LiveAvatar event
repeat	avatar.speak_text
chat	avatar.speak_response
interrupt	avatar.interrupt

The event-driven approach improves responsiveness and reduces latency.

Avatars and Knowledge Bases

• Avatar listing split into List Public Avatars and List User Avatars
• Knowledge Base renamed to Context (all CRUD operations updated)

API keys

HeyGen API keys are not compatible with LiveAvatar. You need a new key from app.liveavatar.com/developers.