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

# Zoom via SDK and RTMS

> Join Zoom meetings through the Zoom SDK and RTMS rather than the web client, for rooms and configurations the browser bot cannot enter.

**Can Vexa join Zoom through the Zoom SDK or RTMS?**

**Today:** No. Zoom joins via the web client in 0.12.x; the native SDK and OBF-token path is not carried.

**Sponsorable:** yes — The SDK and RTMS route, for the meetings the web client cannot reach.

***

*Reach Zoom meetings the browser bot cannot enter.*

|                 |                                    |
| --------------- | ---------------------------------- |
| **Status**      | **sponsorable**                    |
| **Size**        | L                                  |
| **North star**  | 1 · Capture anywhere, owned by you |
| **Measured by** | platforms and routes covered       |

## What it does

* Joins through the Zoom SDK and RTMS rather than the web client.
* Covers rooms and configurations that refuse a browser guest.
* Sits alongside the existing web-client route, not instead of it.

## What exists today

Zoom joins via the **web client** in 0.12.x. The native SDK and OBF-token path is not carried.

## What this adds

The SDK and RTMS route, for the meetings the web client cannot reach.

## How sponsorship works

You fund the item. It moves to the front of the queue. You co-write the acceptance criteria, so "done" means done on your meetings. Your name goes on the release note. Sponsorship buys **the order of the queue** — never exclusivity, never a private build, and never a date the work has not earned. The fee basis is per item or per stage, agreed in writing before work begins.

## Two doors

<Columns cols={2}>
  <Card title="Sponsor this" icon="handshake" color="#0D9373" href="https://cal.com/dmitrygrankin/web?utm_source=docs&utm_medium=roadmap&utm_campaign=sponsor&utm_content=zoom-sdk-rtms" horizontal arrow cta="Book fifteen minutes">
    Fifteen minutes. Bring the constraint you are under.
  </Card>

  <Card title="Watch this" icon="envelope" color="#0D9373" href="mailto:dmitry@vexa.ai?subject=Roadmap%20update%3A%20Zoom%20via%20SDK%20and%20RTMS&body=watch" horizontal arrow cta="Email me">
    One email when it ships. The mail is already written — send it as it is.
  </Card>
</Columns>

## Questions

<AccordionGroup>
  <Accordion title="Can Vexa join Zoom through the Zoom SDK or RTMS?">
    No. Zoom joins via the web client in 0.12.x; the native SDK and OBF-token path is not carried.
  </Accordion>

  <Accordion title="What would sponsoring this add?">
    The SDK and RTMS route, for the meetings the web client cannot reach.
  </Accordion>

  <Accordion title="What happens when it ships?">
    It ships upstream under Apache-2.0, to everyone, with the sponsor named on the release note.
  </Accordion>
</AccordionGroup>

***

*Ships upstream Apache-2.0 when sponsored.*