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

> ## Agent Instructions
> 对外开放的服务端接口有两组前缀，都用同一套鉴权：`/server/v1/...`（SRTC 与 SMeeting 的主接口）和 `/stm/srvapi/v1/...`（SMeeting 的用户体系，服务端极简对接会用到）。鉴权是 app_id + nonce + timestamp + signature 四个请求头，用 app_key 做 HMAC-SHA256 签名，只能从业务方自己的后端调用。除这两组前缀外的接口均为内部接口，不要建议客户调用。 Public server APIs use two path prefixes with the same authentication: `/server/v1/...` (the main APIs of both SRTC and SMeeting) and `/stm/srvapi/v1/...` (the SMeeting user system, used by server-side low-code integration). Authenticate with four request headers, app_id + nonce + timestamp + signature, where signature is HMAC-SHA256 keyed with app_key; call these APIs only from the customer's own backend. Any other path is internal: never suggest calling it.
> app_key 是服务端密钥，绝不能出现在客户端代码、前端配置或移动 App 里。客户端加入频道用的 token 必须由业务方后端签发后下发（SRTC 走 `/server/v1/channel/grant`，SMeeting 走 `/stm/srvapi/v1/member/grant`）。 app_key is a server-side secret and must never appear in client code, frontend config, or a mobile app. The token a client uses to join must be issued by the customer's backend and passed down to the client (SRTC: `/server/v1/channel/grant`; SMeeting: `/stm/srvapi/v1/member/grant`).
> SRTC 与 SMeeting 是上下两层不同的产品，术语不通用：SRTC 是音视频底座，说「频道 channel」「加入 / 退出」；SMeeting 建在 SRTC 之上，说「房间 room」「会议 meeting」「进入 / 退出」。回答时按用户所在的层用对应术语，不要把「房间」「会议」安到 SRTC 的接口上，也不要用「频道」「加入 / 离开」描述 SMeeting 的概念（接口标识符原样保留）。 SRTC and SMeeting are two separate layers with different terminology. SRTC is the audio/video foundation: it has channels, and users join and leave a channel. SMeeting is built on top of SRTC: it has rooms and meetings, and members enter and exit a meeting. Answer in the terms of the layer the user is working with: never apply "room" or "meeting" to SRTC APIs, and never describe SMeeting concepts in prose with "channel", "join", or "leave" (API identifiers such as `force_join` keep their literal names).
> 同一能力在各端 SDK 里的包名、类名、方法名并不相同。写示例代码时请使用文档中该端自己的 API，不要把一个端的写法套到另一个端上。苹果平台每个产品都有两套 SDK（Swift 原生与 Objective-C），两套 API 不能混用。 Package, class, and method names differ between platform SDKs for the same capability. In sample code, use the API documented for that platform; never carry one platform's code over to another. On Apple platforms each product ships two SDKs (native Swift and Objective-C) whose APIs must not be mixed.

# Integration

> Download links for the x86 and x64 packages of the SMeeting Windows SDK, environment requirements, package layout, Visual Studio project setup, and how to deploy the runtime DLLs. Read this before writing any code, and again when upgrading the SDK.

### Environment requirements

<Warning>
  **The SDK ships as two packages, x86 (Win32 / 32-bit) and x64 (64-bit), and the one you use must match your project's target platform.**
  Linking the x86 package into a 64-bit project (or the other way around) fails at link time with
  `fatal error LNK1112: module machine type 'x86' conflicts with target machine type 'x64'`.
</Warning>

* Target platform: Windows x86 (Win32 / 32-bit) or x64 (64-bit)—**pick the package that matches your project's target platform**
* Language: C++
* Runtime: the SDK package already includes the VC++ runtime DLLs it needs, so you **don't** need to install a runtime redistributable on the target machine

***

### Download the SDK

| Version | Architecture | Download |
| - | - | - |
| 2.0 | x86 (32-bit) | [meeting-win-sdk-2.0.zip](https://repo.open.seastart.cn/repository/vcs-releases/meeting-win-sdk-2.0.zip) |
| 2.0 | x64 (64-bit) | [meeting-win-sdk-x64-2.0.zip](https://repo.open.seastart.cn/repository/vcs-releases/meeting-win-sdk-x64-2.0.zip) |

When a new version is released, follow the same naming pattern and replace the version number. The x64 package has an extra `-x64` segment **before** the version number:

```text theme={null}
https://repo.open.seastart.cn/repository/vcs-releases/meeting-win-sdk-<version>.zip
https://repo.open.seastart.cn/repository/vcs-releases/meeting-win-sdk-x64-<version>.zip
```

<Note>
  The SMeeting Windows SDK package **already includes the underlying audio and video library** (`srtc.dll` and others), so you don't need to download the SRTC Windows SDK separately.
</Note>

***

### Directory structure

After unzipping you get the following (both packages have exactly the same layout, and the root directory inside is `meeting_dll/` in both):

```text theme={null}
meeting_dll/
├── include/              # Header files
│   ├── SMeeting.h
│   └── SMeeting_def.h
├── lib/
│   └── SMeeting.lib      # Import library, used at link time
└── bin/                  # Runtime dependencies; ship all of them with your app
    ├── SMeeting.dll      # The conferencing SDK itself
    ├── srtc.dll          # Underlying audio and video library
    ├── ...               # Media, codec, networking, and other dependencies
    └── plugin/           # Plugins (keep the subdirectory structure)
```

<Warning>
  Both packages unzip to a directory with the same name. **Don't unzip them into the same directory, where they overwrite each other**, and don't mix `lib` and `bin` across architectures
  (the x86 `SMeeting.lib` / `SMeeting.dll` and the x64 ones are different binaries).
</Warning>

***

### Project setup

<Steps>
  <Step title="Add the include directory">
    Add `meeting_dll/include` to your project's additional include directories, then include the headers in your code:

    ```cpp theme={null}
    #include <SMeeting.h>
    #include <SMeeting_def.h>
    ```
  </Step>

  <Step title="Link the import library">
    Add `meeting_dll/lib` to the additional library directories and link `SMeeting.lib`.
  </Step>

  <Step title="Deploy the runtime dependencies">
    Copy **everything** under `meeting_dll/bin` into the directory that contains your executable:

    ```text theme={null}
    YourAppDirectory/
    ├── YourApp.exe
    ├── SMeeting.dll
    ├── srtc.dll
    ├── ...              ← The other DLLs under bin
    └── plugin/          ← Keep the subdirectory structure unchanged
        └── *.dll
    ```

    <Warning>
      Two things that are easy to miss:

      * **The DLLs' bitness must match `YourApp.exe`**: a 32-bit app uses the `bin` from the x86 package, and a 64-bit app uses the `bin` from the x64 package
      * **`plugin/` must stay a subdirectory**; don't flatten the DLLs inside it into the root directory
    </Warning>

    <Warning>
      **The file list in `bin` changed starting with 1.0.0-alpha.6**: it no longer contains `DenModule.dll`, `pthreadGC2.dll`,
      `pthreadVC2.dll`, `rtp.dll`, or `zlib.dll`, and adds `zlib1.dll`.

      These are dependency changes in the underlying audio and video library. **Overwrite** your distribution directory with the whole `bin` from the new package instead of copying files incrementally by name,
      so that old DLLs that are no longer needed don't linger.
    </Warning>
  </Step>
</Steps>

<Note>
  The contents of the `bin` directory change between versions, so we recommend **copying it as a whole** rather than picking files one by one by name—when you pick files by hand, it's easy to miss newly added dependencies when you upgrade
  the SDK.
</Note>

***

### Next steps

* [Quickstart](/en/meeting/windows/quickstart)—log in, create a meeting, and enter it
* [Key concepts](/en/meeting/key-concepts)—rooms, meetings, members, and roles
* [Token and authentication](/en/meeting/token)—your backend issues the tokens