​
Manage Meets

Create and manage meet deployments for your organization. A deployment points at an assistant or workflow and exposes a public slug that visitors can use to start sessions.

​
Create a meet

​
Endpoint

​
Request Body

​
name
string
required
Display name for the meet deployment
​
slug
string
URL slug used in public meet links (auto-generated if omitted)
​
assistant_id
string
Assistant UUID to run in the meet
​
workflow_id
string
Workflow UUID to run in the meet (alternative to assistant_id)
​
avatar_id
string
Optional deployment-level avatar. For workflow Meets, omit this field when the workflow Start, Agent, and Subagent nodes manage avatars. It is only used by a Start node configured to inherit the deployment avatar.
​
rotating_code_enabled
boolean
Whether visitors must enter a rotating code before starting a session
​
code_rotation_interval_minutes
integer
How often the code rotates (e.g. 60)
​
access_mode
string
Access control mode: open or rotating_code
​
allow_visual_input
boolean
Permit camera/screen input from visitors

​
Example Request

​
List meets

​
Get / Update / Delete

​
Codes

Rotate the current access code immediately (e.g. after a leak):
Read the current valid code (for sharing with visitors):

​
Response

​
Public meet info

Returns the deployment’s public configuration (name, whether a code is required) without authentication.

​
Workflow Meets and avatars

workflow_id and assistant_id are mutually exclusive. A workflow Meet does not require avatar_id:
With no deployment avatar, the Meet starts normally and the workflow’s Start avatar scope decides whether to attach a visual avatar. If Start inherits and no deployment avatar exists, the session stays voice-only until a later Agent or Subagent selects an avatar. Phone sessions never create an avatar.

​
Errors