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

# addMultipleParticipants

> Only the meeting host can add participants. Validates each user and skips those who
are already participants or don't exist. Returns lists of successfully added participants
and skipped entries with reasons. Updates the meeting's participant count automatically.



## OpenAPI

````yaml api-reference/convex-openapi.yaml post /api/run/meetings/lifecycle/addMultipleParticipants
openapi: 3.0.3
info:
  title: Connvo Convex API
  version: 1.0.0
  description: >-
    HTTP interface for Connvo's Convex backend, exposing vetted query, mutation,
    and action endpoints.
servers:
  - url: https://Connvo-dev.convex.cloud
    description: Dev Convex deployment
  - url: https://Connvo-staging.convex.cloud
    description: Staging Convex deployment
  - url: https://Connvo-prod.convex.cloud
    description: Prod Convex deployment
security:
  - bearerAuth: []
tags:
  - name: Users
    description: Identity, profile, and authentication operations for Connvo users.
  - name: Meetings
    description: Scheduling, managing, and retrieving meeting data.
  - name: Transcripts
    description: Endpoints for accessing call transcripts and transcription controls.
  - name: Insights
    description: AI-generated insights, summaries, and analytics derived from meetings.
  - name: Prompts
    description: Prompt management and AI conversation guidance.
  - name: Notes
    description: Collaborative meeting notes and follow-up documentation.
  - name: WebRTC
    description: Real-time communication, session signalling, and media utilities.
  - name: System
    description: General system endpoints such as health checks and diagnostics.
paths:
  /api/run/meetings/lifecycle/addMultipleParticipants:
    post:
      tags:
        - Meetings
      summary: addMultipleParticipants
      description: >-
        Only the meeting host can add participants. Validates each user and
        skips those who

        are already participants or don't exist. Returns lists of successfully
        added participants

        and skipped entries with reasons. Updates the meeting's participant
        count automatically.
      operationId: postApiRunMeetingsLifecycleAddMultipleParticipants
      requestBody:
        content:
          application/json:
            schema:
              $ref: >-
                #/components/schemas/Request_meetings.lifecycle.addMultipleParticipants
            example:
              args:
                meetingId: meeting_123example
                participants:
                  - userId: user_456example
                    role: participant
                  - userId: user_789example
                    role: participant
                  - userId: user_012example
                    role: observer
        required: true
      responses:
        '200':
          description: Convex executed your request and returned a result
          content:
            application/json:
              schema:
                $ref: >-
                  #/components/schemas/Response_meetings.lifecycle.addMultipleParticipants
              example:
                status: success
                errorMessage: ''
                errorData: {}
                value:
                  added:
                    - participant_456example
                    - participant_789example
                  skipped:
                    - userId: user_012example
                      reason: User not found
                  success: true
        '400':
          description: Failed operation
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/FailedResponse'
        '500':
          description: Convex Internal Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/FailedResponse'
      security:
        - bearerAuth: []
components:
  schemas:
    Request_meetings.lifecycle.addMultipleParticipants:
      type: object
      required:
        - args
      properties:
        args:
          type: object
          required:
            - meetingId
            - participants
          properties:
            meetingId:
              type: string
              description: ID from table "meetings"
            participants:
              type: array
              items:
                type: object
                required:
                  - role
                  - userId
                properties:
                  role:
                    oneOf:
                      - type: string
                        enum:
                          - host
                      - type: string
                        enum:
                          - co-host
                      - type: string
                        enum:
                          - participant
                      - type: string
                        enum:
                          - observer
                  userId:
                    type: string
                    description: ID from table "users"
    Response_meetings.lifecycle.addMultipleParticipants:
      type: object
      required:
        - status
      properties:
        status:
          type: string
          enum:
            - success
            - error
        errorMessage:
          type: string
        errorData:
          type: object
        value:
          type: object
          required:
            - added
            - skipped
            - success
          properties:
            added:
              type: array
              items:
                type: string
                description: ID from table "meetingParticipants"
            skipped:
              type: array
              items:
                type: object
                required:
                  - reason
                  - userId
                properties:
                  reason:
                    type: string
                  userId:
                    type: string
                    description: ID from table "users"
            success:
              type: boolean
    FailedResponse:
      type: object
      properties: {}
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: >-
        Standard user authentication token issued via WorkOS. Provide as
        `Authorization: Bearer <user-token>`.

````