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

# Device integration and IM

> SMeeting reuses the SRTC device integration and IM endpoints as-is. Explains the two differences when calling them through SMeeting (domain and signing credentials) and why a device's target is the meeting_id, not the room number.

For integrating SIP / H.323 / GB28181 and other devices, and for out-of-meeting IM messages, SMeeting doesn't provide a separate set of endpoints—
requests are forwarded as-is to the underlying SRTC, with exactly the same parameters and response structure.

So the documentation for these two groups of endpoints is the two SRTC pages:

<Columns cols={2}>
  <Card title="Device integration" href="/en/rtc/server-api/agent">
    Add, delete, update, and query devices, list gateways, invite devices, and turn device audio and video on or off during the meeting
  </Card>

  <Card title="IM messages" href="/en/rtc/server-api/im">
    Out-of-meeting instant messages, IM grants, and device online status management
  </Card>
</Columns>

### Two differences when calling them

**Use the SMeeting domain**. The endpoint paths (`/server/v1/agent/...`, `/server/v1/im/...`) and parameters
stay the same; you just send the requests to the SMeeting address, with no need to integrate with the SRTC domain separately.

**Sign with the SMeeting app\_id / app\_key as well**. For the signing algorithm, see the [Overview](/en/meeting/server-api/overview).
Authentication is already done at the SMeeting layer when requests are forwarded.

### What to use as the target when a device enters the meeting

The `no` parameter of inviting a device (`/server/v1/agent/invite`) is the target channel name. In SMeeting,
**the meeting ID (`meeting_id`) is the channel name at the RTC layer**, so pass `meeting_id` directly as `no`.

Note that it's not the room number `room_no`—that is the number users enter in the client, and one room can host several meetings
one after another. Only `meeting_id` uniquely identifies the specific meeting the device should enter.