> ## 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. # Add a visitor to a Dyte meeting > Adds the visitor represented by the signed widget session to the meeting referenced by an integration message in that same visitor conversation. Send website_token and X-Auth-Token as for other widget endpoints; the message lookup is scoped to conversations from the session. The account must have Dyte connected for the operation to succeed. A successful response includes a secret-bearing participant `token`; do not log or persist it. ## OpenAPI ````yaml /api-reference/openapi.json post /api/v1/widget/integrations/dyte/add_participant_to_meeting openapi: 3.0.4 info: title: Tied API description: >- The Tied REST API. Three families of endpoint, each with its own credential: **Application** for everything inside an account, **Platform** for provisioning accounts and users, and **Client** for acting as a contact from your own surface. version: 1.1.0 termsOfService: https://tied.com/legal contact: email: hello@tied.com license: name: MIT License url: https://opensource.org/licenses/MIT servers: - url: https://app.tied.com description: Tied cloud security: [] tags: - name: Account AgentBots description: Account-specific Agent Bots - name: Agents description: Agent management APIs - name: Canned Responses description: Pre-defined responses for common queries - name: Contacts description: Contact management APIs - name: Contact Labels description: Manage contact labels - name: Conversation Assignments description: Manage conversation assignments - name: Conversation Labels description: Manage conversation labels - name: Conversations description: Conversation management APIs - name: Custom Attributes description: Custom fields for contacts and conversations - name: Custom Filters description: Saved filters for conversations - name: Inboxes description: Communication channels setup - name: Integrations description: Third-party integrations - name: Messages description: Message management APIs - name: Profile description: User profile APIs - name: Reports description: Analytics and reporting APIs - name: Teams description: Team management APIs - name: Webhooks description: Event notification webhooks - name: Automation Rule description: Workflow automation rules - name: Help Center description: Knowledge base management - name: Contacts API description: Public contact APIs - name: Conversations API description: Public conversation APIs - name: Messages API description: Public message APIs - name: CSAT Survey Page description: Customer satisfaction survey - name: Account description: >- The authenticated user's own account — read and update account settings. Distinct from the Platform family's **Accounts**, which provisions accounts across an installation. - name: Audit Logs description: Read the account's audit trail - name: Inbox API description: Public inbox lookup by channel identifier - name: Labels description: >- Create and manage the account's labels. Applying one to a conversation or contact is a separate endpoint under those resources. - name: Macros description: >- Saved multi-step actions an agent — or an integration — can run against one or more conversations. - name: Campaigns description: Ongoing website campaigns and one-off SMS and WhatsApp sends. - name: Contact Notes description: Internal notes on a contact. Never visible to the contact. - name: Help Center Categories description: Categories group a portal's articles, one tree per allowed locale. - name: Help Center Articles description: The articles a portal publishes, and their draft and archived states. - name: Summary Reports description: Per-agent, per-team, per-inbox and per-label totals for a period, as JSON. - name: Live Reports description: Right-now queue counts. No date range — these describe the present. - name: CSAT description: >- The satisfaction ratings contacts have submitted, and the metrics computed from them. - name: Notifications description: >- The per-user notification feed, its read and snooze state, and the settings that decide what lands in it. - name: Conversation Participants description: >- The agents watching a conversation. Participants get notified about it without being assigned to it. - name: Draft Messages description: >- The unsent reply held for a conversation. Stored in Redis, one per conversation. - name: Search description: >- One search service across conversations, contacts, messages and Help Center articles. - name: Dashboard Apps description: Embedded pages that appear as a tab beside a conversation. - name: Assignment Policies description: How conversations are handed out, and which inbox uses which policy. - name: Files description: Storing a file so another endpoint can attach it. - name: Bot Flows description: >- Scripted conversation flows, their versions, and the publish and rollback that move between them. - name: Billing description: >- Credit balance, usage, invoices, spend controls and the provider-hosted payment flows. - name: AMB Templates description: >- Saved Apple Messages primitive payloads an agent can reuse from the composer. - name: AMB Onboarding description: The in-flight Apple Messages for Business registration for an account. - name: Widget Session description: Starting a widget session and reading the visitor it belongs to. - name: Widget Conversation description: The visitor's conversation and its messages. - name: Widget Context description: Campaigns, agents, labels, events and uploads for a widget session. - name: CSAT Survey description: The public, unauthenticated survey a contact answers from a link. - name: Workspace description: Scheduling and cancelling deletion of the whole workspace. - name: Widget Integrations description: Provider actions available to a visitor session in its own conversation. - name: Orchestration Studio description: >- Administrator-only read APIs for Orchestration Studio cases and knowledge sources. - name: Topic Analytics description: Account Topics readiness, labeling health and usage aggregates. paths: /api/v1/widget/integrations/dyte/add_participant_to_meeting: post: tags: - Widget Integrations summary: Add a visitor to a Dyte meeting description: >- Adds the visitor represented by the signed widget session to the meeting referenced by an integration message in that same visitor conversation. Send website_token and X-Auth-Token as for other widget endpoints; the message lookup is scoped to conversations from the session. The account must have Dyte connected for the operation to succeed. A successful response includes a secret-bearing participant `token`; do not log or persist it. operationId: add-widget-dyte-meeting-participant parameters: - $ref: '#/components/parameters/website_token' requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/dyte_widget_add_participant_payload' example: message_id: 104 responses: '200': description: >- Participant created for the visitor session. `token` is a secret-bearing provider token. content: application/json: schema: $ref: '#/components/schemas/dyte_participant_response' example: id: synthetic-id token: SYNTHETIC_REDACTED '401': description: >- The website token belongs to a suspended account; no participant request is sent to Dyte. content: application/json: schema: $ref: '#/components/schemas/dyte_error_response' '404': description: >- The widget session, message, or Dyte integration cannot be found. Invalid visitor sessions and disconnected Dyte integrations also return this 404 JSON body. content: application/json: schema: $ref: '#/components/schemas/dyte_error_response' example: error: Resource could not be found '422': description: >- The selected message is not a Dyte integration message or the provider rejected the request. content: application/json: schema: $ref: '#/components/schemas/dyte_error_response' examples: invalidMessage: summary: Selected message is not a Dyte integration message. value: error: Invalid message type. Action not permitted providerRejected: summary: Provider rejected the operation. value: error: success: false data: message: Participant is invalid error_code: 422 security: - widgetAuthToken: [] components: parameters: website_token: name: website_token in: query required: true description: >- The web-widget inbox's public token, as it appears in your widget snippet. Required on every widget request. schema: type: string example: EXAMPLE_WEBSITE_TOKEN schemas: dyte_widget_add_participant_payload: type: object required: - message_id description: >- Request to add the visitor represented by the current widget session to the meeting card in that visitor conversation. properties: message_id: type: integer description: >- The message ID of the Dyte integration card in the current visitor conversation. example: message_id: 104 dyte_participant_response: type: object description: >- Provider participant identity and join token. The `token` field is secret-bearing and should be held only as long as needed to join the meeting. required: - id - token properties: id: type: string description: Provider participant identifier. token: type: string description: >- Synthetic in examples; in a real response this is a secret-bearing, short-lived participant token. example: id: synthetic-id token: SYNTHETIC_REDACTED dyte_error_response: type: object description: A request or provider error. Provider error details vary. properties: error: oneOf: - type: string description: A local validation or not-found message. - type: object description: Provider error envelope. additionalProperties: true description: Error details. error_code: type: integer description: >- HTTP status returned by the provider, when the failure came from Dyte. errors: type: array items: type: string description: >- Authentication failures without a signed-in user may use an errors list. securitySchemes: widgetAuthToken: type: apiKey in: header name: X-Auth-Token description: >- The signed session token from `POST /api/v1/widget/config`. Sent alongside `website_token` in the query string on every widget request. See /api-reference/widget-api-authentication. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.