> ## Documentation Index > Fetch the complete documentation index at: https://docs.orbit.devotel.io/llms.txt > Use this file to discover all available pages before exploring further. # Post a chat message into a video room > Broadcasts a chat message to every participant on the room's `orbit.chat` data-channel topic. Any joined participant may post (mirrors reactions / Q&A) — an SDK bot or webinar viewer included. Chat is transient: the message is fanned out, never persisted, so there is no list to read back. The sender identity is SERVER-stamped from the auth context and is never a body field; the caller mints the `message_id` UUID so the stateless send → delete lifecycle correlates client-side. Scoped on `video:read` (or `video:write` as a superset). ## OpenAPI ````yaml /openapi.yaml post /api/v1/video/rooms-scheduled/{id}/chat openapi: 3.1.0 info: title: Devotel CPaaS API description: Orbit by Devotel — Communications Platform as a Service API version: 1.0.0 contact: name: Devotel url: https://devotel.io email: support@devotel.io license: name: Proprietary servers: - url: https://api.orbit.devotel.io description: Production security: - Bearer: [] - ApiKey: [] tags: - name: Messages description: >- Send and manage messages across all channels (SMS, WhatsApp, RCS, Email, Viber, etc.) - name: Fax description: >- List and track fax (MMS/T.38) transmissions on Telnyx-backed fax numbers (sending flows through the Messaging API) - name: Agents description: AI agent creation, configuration, and execution - name: Voice description: Voice calls, IVR, conferencing, and SIP trunking - name: OnCall description: On-call rotations and escalation policy planning for incident alerting - name: Webhooks description: Webhook endpoint management and delivery logs - name: Numbers description: Phone number search, provisioning, and configuration - name: Brand Identity description: >- Unified cross-channel brand trust posture (10DLC, toll-free, WhatsApp, RCS, branded calling, number KYC) - name: Contacts description: Contact management, segmentation, and lifecycle tracking - name: Campaigns description: Marketing campaign orchestration and analytics - name: Flows description: Automation flow builder and execution engine - name: Templates description: Message template management and approval workflows - name: Settings description: Organization, channel, and user preference settings - name: Verify description: OTP generation and verification across channels - name: Push description: Push notification delivery via FCM and APNs - name: Integrations description: Third-party service connections and OAuth management - name: CDP description: >- Customer Data Platform — activation surface (CRM object sync, streaming destinations, ad-audience activation) - name: Files description: >- Server-to-server media upload, listing, retrieval, and deletion (signed-URL backed) - name: Commerce description: >- Omnichannel conversational-commerce — persistent cart + checkout state machine, channel-agnostic hosted pay-by-link, native WhatsApp checkout, and AP2-style agent payment mandates. - name: Sync description: >- Real-time shared-state primitive (Twilio Sync parity) — Documents, Maps, Lists, and ephemeral Streams, with change events relayed over the /api/v1/ws/sync WebSocket gateway paths: /api/v1/video/rooms-scheduled/{id}/chat: post: tags: - Video summary: Post a chat message into a video room description: >- Broadcasts a chat message to every participant on the room's `orbit.chat` data-channel topic. Any joined participant may post (mirrors reactions / Q&A) — an SDK bot or webinar viewer included. Chat is transient: the message is fanned out, never persisted, so there is no list to read back. The sender identity is SERVER-stamped from the auth context and is never a body field; the caller mints the `message_id` UUID so the stateless send → delete lifecycle correlates client-side. Scoped on `video:read` (or `video:write` as a superset). parameters: - schema: type: string in: path name: id required: true description: Scheduled room id. requestBody: required: true content: application/json: schema: type: object required: - message_id - text properties: message_id: type: string format: uuid description: Client-minted UUID correlating the send → delete lifecycle. text: type: string minLength: 1 maxLength: 2000 description: >- The message text. The sender identity is never a body field — the server stamps it. reply_to: type: string format: uuid description: >- Optional `message_id` of the message being replied to (threaded replies). responses: '200': description: Message broadcast to the room. content: application/json: schema: type: object properties: data: type: object properties: message_id: type: string format: uuid description: >- Echoes the client-minted message id that was broadcast. meta: type: object properties: request_id: type: string timestamp: type: string format: date-time description: ISO 8601 UTC timestamp of the response '400': description: Default Response content: application/json: schema: type: object properties: error: type: object required: - code - message - status properties: code: type: string description: >- Machine-readable error code (e.g. INVALID_PHONE_NUMBER) message: type: string description: Human-readable error description status: type: integer description: HTTP status code details: type: object additionalProperties: true description: Additional context about the error meta: type: object properties: request_id: type: string timestamp: type: string format: date-time docs_url: type: string format: uri description: Link to relevant error documentation components: securitySchemes: Bearer: type: http scheme: bearer bearerFormat: JWT description: Dashboard JWT token from Clerk ApiKey: type: apiKey name: X-API-Key in: header description: Server-to-server API key (dv_live_sk_*) ````