> ## 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.

# C++ API reference

> Entry point to the SMeeting Windows SDK C++ API: how the engine-level ISMeetingEngine and meeting-level ISMeetingChannel split the work, their event and setting interfaces, the vtable recompilation rule, and an index of every API module page.

This page is the complete reference for the SMeeting Windows SDK C++ API. All APIs are defined in the `SMeeting.h` header file.

Starting with `1.0.0-alpha.5`, `ISMeetingEngine` is split into two sets of interfaces (**engine level / meeting level**):

| Interface | Scope | Description |
| - | - | - |
| [ISMeetingEngine](/en/meeting/windows/api-reference/smeeting-engine) | Engine level | Login, meeting management HTTP APIs, channel object lifecycle, device enumeration, IM, and the resource drive. |
| [ISMeetingChannel](/en/meeting/windows/api-reference/smeeting-channel) | Meeting level | One object per meeting, covering entering the meeting, in-meeting operations, and media objects. |
| [ISMeetingEngineEvent](/en/meeting/windows/api-reference/smeeting-events) | Engine-level callbacks | Device, network probe, and IM events. |
| [ISMeetingChannelEvent](/en/meeting/windows/api-reference/smeeting-events) | Meeting-level callbacks | In-meeting events such as connection state, members, room, and media streams. |
| [ISMeetingSetting](/en/meeting/windows/api-reference/smeeting-settings) | Engine-level settings | Only `sdk_log_path` / `enable_stream_log`. |
| [ISMeetingChannelSetting](/en/meeting/windows/api-reference/smeeting-settings) | Meeting-level settings | Streaming mode, statistics interval, display name and avatar for entering the meeting, and more. |

**Important**: `ISMeetingEngine` / `ISMeetingChannel` and the `IMEET*` family are all pure virtual interfaces, and any signature change alters the vtable. After upgrading the SDK you must recompile your project; replacing only the DLLs is not enough.

***

## API module index

* [ISMeetingEngine engine API](/en/meeting/windows/api-reference/smeeting-engine)—initialization, login and logout, meeting management, channel object management, device enumeration, IM, and the resource drive.
* [ISMeetingChannel meeting API](/en/meeting/windows/api-reference/smeeting-channel)—entering / exiting the meeting, room info, user operations, and the waiting room.
* [Host management APIs](/en/meeting/windows/api-reference/smeeting-admin)—room controls, member controls, and permission management.
* [Sub-meeting APIs](/en/meeting/windows/api-reference/smeeting-submeeting)—create / start / stop sub-meetings and move members between them.
* [MCU APIs](/en/meeting/windows/api-reference/smeeting-mcu)—composite video and recording configuration.
* [Sign-in APIs](/en/meeting/windows/api-reference/smeeting-signin)—create sign-in activities, get statistics, and export them.
* [Media track APIs](/en/meeting/windows/api-reference/smeeting-media)—local / remote audio and video, screen sharing, custom tracks, and local recording.
* [Event callbacks](/en/meeting/windows/api-reference/smeeting-events)—`ISMeetingEngineEvent` and `ISMeetingChannelEvent`.
* [Settings](/en/meeting/windows/api-reference/smeeting-settings)—`ISMeetingSetting` and `ISMeetingChannelSetting`.
* [Enums and data structures](/en/meeting/windows/api-reference/smeeting-types)—`StatusCode`, `Role`, `SMeetingCreateMeetingModel`, and more.