Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.tavus.io/llms.txt

Use this file to discover all available pages before exploring further.

Outbound: Tavus notifies you when the replica or the user starts or stops speaking, using one event stream and a properties.role field instead of separate user- versus replica-only events.

conversation.started_speaking fires when either party begins speaking; conversation.stopped_speaking when either stops.

​
message_type
string

conversation for conversation-layer app messages.

Example:

"conversation"

​
event_type
enum<string>

conversation.started_speaking or conversation.stopped_speaking.

Available options:
conversation.started_speaking,
conversation.stopped_speaking
Example:

"conversation.started_speaking"

​
seq
integer

Monotonic per event; a higher seq was emitted later. Use with turn_idx as in Event ordering and turn tracking.

Example:

42

​
inference_id
string

Identifier for correlating this speaking span with conversation.utterance, conversation.tool_call, and other events from the same turn.

Example:

"83294d9f-8306-491b-a284-791f56c8383f"

​
turn_idx
integer

Turn index; increments when conversation.respond is processed. Groups utterances, tool calls, and speaking-state events for the same turn. See Event ordering and turn tracking.

Example:

3

​
properties
object

Always includes role ("replica" or "user") identifying who started or stopped speaking.

On conversation.stopped_speaking only, also includes interrupted (whether the speaker was cut off mid-speech before finishing naturally) and duration (how long they spoke, in seconds; may be null if the start time could not be determined).