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

# Overview

> What the SMeeting conferencing SDK (STMLink Meeting) covers, the three integration options from server-side low-code integration to fully custom UI, and supported platforms. Start here to decide how to add video meetings to your product.

SMeeting (the SDK behind STMLink Meeting) is a complete audio and video conferencing SDK. It is built on top of [SRTC audio and video](/en/rtc/overview) and turns the rules that only meetings need—host, raise hand, mute all, waiting room, recording—into ready-made capabilities, so you don't have to implement them again.

Still deciding between SRTC and SMeeting? See [Choosing SRTC or SMeeting](/en/choose) first.

***

## What you can do

| | |
| - | - |
| **Meeting management** | Create, update, and cancel meetings; scheduled and instant meetings; meeting list and details |
| **Audio and video** | Camera, microphone, screen sharing, subscribing to multiple members' video |
| **Meeting controls** | Host / co-host, mute all, remove a member, change roles, lock the meeting |
| **Member interaction** | Raise a hand to request to speak, host asks to unmute, in-meeting chat, custom messages |
| **Meeting features** | Waiting room, sub-meetings, sign-in, roll call |
| **Recording and live streaming** | Server-side MCU stream mixing, recording, layout configuration, re-streaming |
| **Out-of-meeting messages** | A notification path independent of meetings for calls, meeting reminders, help requests, and more (not a chat tool; see [Three types of messages](/en/meeting/key-concepts#three-types-of-messages)) |

***

## Three integration options

Ordered from least to most effort; choose based on how much customization you need:

| Option | What you do | UI | Best for |
| - | - | - | - |
| **Server-side low-code integration** | Your backend calls 3 endpoints and builds a URL | Deployed by us | Attaching meetings to an existing business workflow (reviews, tickets, tendering and bidding) |
| **Low-code integration with UI** | Take our frontend source code, modify it, and deploy it yourself | Our source code, which you can modify | Your own branding with light customization |
| **Custom integration** | Integrate the SDKs for each platform and build your own UI | Entirely your own | Building a meeting product with deeply customized interactions |

### Server-side low-code integration

**You don't integrate any SDK or build a meeting UI.** The meeting client, user system, and login state are already deployed by us. Your backend does only three things: create the meeting, get a login-free token for the user, and redirect the user's browser to the meeting page.

Best for: you want to "add a video meeting entry to this review," not build a meeting product.

Start with [Server-side low-code integration](/zh/meeting/ui-sdk/server-integration) (Chinese).

### Low-code integration with UI

Bring in the meeting UI source code we provide, deploy it yourself, and adapt it as needed; on the server side, you only need to connect the accounts.

Best for: you want to launch quickly, but the UI must match your brand.

See [Web](/zh/meeting/ui-sdk/web) (Chinese) · [iOS](/zh/meeting/ui-sdk/ios) (Chinese) · [Android](/zh/meeting/ui-sdk/android) (Chinese) · [Windows](/zh/meeting/ui-sdk/windows) (Chinese).

### Custom integration

You build the UI yourself and call the SDK for each platform to implement meeting features; your server calls the meeting backend APIs and exposes a callback endpoint to receive events.

Best for: the UI must follow your own design guidelines, and the interaction flows need customization.

Choose your platform from the platform support table below.

***

## Platform support

| Platform | Docs |
| - | - |
| Web | [Web SDK](/en/meeting/web/integration) |
| Android | [Android SDK](/en/meeting/android/integration) |
| Windows | [Windows SDK](/zh/meeting/windows/integration) (Chinese) |
| iOS / macOS (Swift) | [Swift SDK](/en/meeting/swift/integration) |
| iOS (Objective-C) | [iOS SDK](/zh/meeting/ios/quickstart) (Chinese) |
| Server | [Server API](/en/meeting/server-api/overview) |

<Note>
  For WeChat Mini Program scenarios, we recommend embedding a page built with the Web SDK through `<web-view>`, so that one codebase covers both browsers and mini programs. See [Web SDK integration](/en/meeting/web/integration).
</Note>

***

## Next steps

* [Quickstart](/en/meeting/quickstart)—an overview of the integration flow
* [Key concepts](/en/meeting/key-concepts)—rooms, meetings, members, and roles
* [Token and authentication](/en/meeting/token)—the grant flow and secret key security