active, the bot does three things, and you choose how each is driven:
- Speak — say text out loud, and stop mid-utterance.
- Chat — post to the meeting’s native chat.
- Automate — hand the speaking to a Telnyx AI Assistant, which listens and answers on its own.
send_chat keeps working exactly as it does without one. speak is not refused with an assistant attached: the bot becomes a webpage-output bot and speak audio routes through the assistant’s output page instead of the bot mic (see Speak). The assistant is still meant to do the talking, so pick between speaking modes before the meeting rather than discovering the difference during it; Telnyx AI Assistants sets out what the assistant takes over.
All manual actions return 202 Accepted and complete asynchronously.
Same Commands over WebSocket
The same actions can be sent as frames on the live transcript stream instead of over REST:Errors
Action requests fail with a non-2xx status and an error envelope, for example when the session is notactive:
Every code the Meeting API returns is listed in Meeting API Errors.
Related
- Speak — make the bot say something, and stop it
- Chat — post to the meeting chat and read replies
- Telnyx AI Assistants — let an assistant hold the conversation
- Live Transcript — follow the transcript stream in real time