For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Ask AIPlaygroundLoginFree API Key
HomeAPI ReferenceVoice AgentSpeech-to-TextText-to-SpeechIntelligenceSelf-Hosted Deployments
HomeAPI ReferenceVoice AgentSpeech-to-TextText-to-SpeechIntelligenceSelf-Hosted Deployments
  • Get Started
    • Overview
    • Build a Voice Agent
    • Feature Overview
    • Template Apps
  • Configure
    • Overview
    • STT Models
    • LLM Models
    • TTS Models
    • Media Inputs & Outputs
    • Prompting Voice Agents
    • Multilingual Voice Agents
    • Maintaining Context
    • Reusable Agent Configurations
  • Build
    • Multi-Agent Architecture
  • Connect
  • Controls
      • Overview
      • Welcome
      • Settings Applied
      • Conversation Text
      • User Started Speaking
      • Agent Thinking
      • Acknowledgements
      • Agent Audio Done
      • Errors & Warnings
      • History
  • Optimize
    • Voice Agent TTS Controls
    • Message Flow
    • Audio & Playback
    • Audio Preprocessing & Barge-In
    • Adaptive Echo Cancellation
  • Resources
    • SDKs
    • UI Components
    • API Reference
LogoLogo
Ask AIPlaygroundLoginFree API Key
On this page
  • List of Server Events
ControlsOutputs: Server Events

Outputs: Server Events

Server messages you will receive from the Agent server.
Was this page helpful?
Previous

Welcome

Receive a welcome message from the server to confirm the websocket has opened.
Next
Built with

Server Events are messages sent from the Deepgram server to the client over the WebSocket connection during a voice agent interaction. These events provide real-time updates about the conversation’s status, including user and agent actions, as well as any processing that’s occurring.

List of Server Events

  • Welcome: Confirms that the WebSocket has opened successfully.
  • Settings Applied: Confirms that the configuration settings have been applied.
  • Conversation Text: Provides the text of what was spoken by either the user or the agent.
  • User Started Speaking: Notifies that the user has begun speaking.
  • Agent Thinking: Informs the client that the agent is processing information.
  • Function Call Request: Sent when the agent needs to make a function call.
  • Function Call Response: Sent to provide information about a function call.
  • PromptUpdated / SpeakUpdated / ThinkUpdated: Server confirms that an Update* message has been applied.
  • Agent Audio Done: Indicates that the server has finished sending the final audio segment to the client.
  • Error / Warning: Server reports a fatal error (Error) or non-fatal issue (Warning).

Each of these events serves a specific purpose in managing the flow of the conversation and keeping the client informed about the state of the interaction. They allow for a dynamic and responsive experience when using Deepgram’s Voice Agent API.