> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tied.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Video meeting integrations

> Create Dyte meetings and add a visitor or account user to one.

## Dyte meetings

The account must have Dyte connected before these operations can succeed. The meeting operation creates a meeting with Dyte and records its meeting identifier in a conversation integration message. The participant operations use that message to add the current account user or the visitor in the current widget session.

The participant response includes `token`, a secret-shaped Dyte join token. Keep it only as long as needed to join the meeting; do not log or persist it.

If Dyte is disconnected, each operation returns `404` with `{"error":"Resource could not be found"}`. The server does not make a provider request in that case.

| Operation | Caller | Request identifier |
| - | - | - |
| [Create a meeting](/api-reference/integrations/create-a-dyte-meeting) | Authenticated account user with access to the conversation | `conversation_id` |
| [Add an account user](/api-reference/integrations/add-a-dyte-meeting-participant) | Authenticated account user with access to the conversation | `message_id` for the Dyte integration message |
| [Add a widget visitor](/api-reference/widget-integrations/add-a-visitor-to-a-dyte-meeting) | Widget website token and visitor session token | `message_id` in that visitor's conversation |

The OpenAPI operations document each request and provider response. They also list the failures returned for missing conversations, invalid message types, authentication failures, and provider rejection.

## Voice

This reference intentionally has no voice operation. Tied's own voice operations belong to the Voice Channel initiative and will be documented when that API ships.

The widget participant operation returns `401` with `{"error":"Account is suspended"}` when the website token belongs to a suspended account. The server does not contact Dyte in that case.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.