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

# Error code format

> How SMeeting error codes are numbered (prefix plus a 3-digit code), how to tell server, cross-platform SDK, and platform-specific errors apart, and why SRTC 1xxxxx codes show up alongside SMeeting 2xxxxx codes. Read this when troubleshooting an error code.

`0` means success; anything other than 0 is an error.

Every error code is structured as **prefix + a 3-digit specific code (001–999)**. Once you can read the prefix, you can tell right away **which layer** and **which platform** the error comes from.

***

## How to read an error code

```text theme={null}
  2 0 3 0 0 1
  │ │ │ └─┴─┴── Specific code 001-999
  │ │ └──────── Platform type: 3 = iOS
  └─┴────────── Product layer: 2 = SMeeting
```

There are three cases:

| Digits | Source | Prefix | Example |
| - | - | - | - |
| 4 digits | Returned by the **server** | `2` | `2xxx` business errors from the meeting service |
| 6 digits, third digit is `0` | Client SDK, **common to all platforms** | `200` | `200xxx` |
| 6 digits | Client SDK, **platform-specific** | `20` + platform type | `203001` iOS error |

***

## Platform types

| Type | Platform | SMeeting prefix |
| :-: | - | - |
| 1 | Windows | `201` |
| 2 | Android phone | `202` |
| 3 | iOS phone | `203` |
| 4 | Linux C/C++ | `204` |
| 5 | macOS | `205` |
| 6 | Web | `206` |
| 7 | Mini Program | `207` |
| 8 | Android set-top box | `208` |
| 9 | Android embedded | `209` |

<Note>
  The Swift SDK supports both iOS and macOS and automatically uses the `203` or `205` prefix depending on the platform it runs on.
</Note>

***

## Why you see error codes starting with 1xxxxx

**This is expected, not a bug.**

SMeeting is built on SRTC. When an error occurs in the underlying audio and video layer, SMeeting passes SRTC's original error code through to you **as-is** instead of wrapping it in its own code—so you can pinpoint which layer the problem is in.

| What you see | Meaning | Where to look |
| - | - | - |
| `2xxx` | The meeting server rejected the request (no permission, meeting doesn't exist, etc.) | [Server API error codes](/en/meeting/server-api/error-codes) |
| `20Nxxx` | An error from the meeting-layer SDK | The error code page for that platform |
| `1xxx` | An error from the underlying SRTC **server** | [SRTC error code format](/en/rtc/error-codes) |
| `10Nxxx` | An error from the underlying SRTC **client** (for example, "not in a channel") | [SRTC error code format](/en/rtc/error-codes) |

So seeing both `203002` and `103002` in the iOS conferencing SDK is not a contradiction: the former is error 002 of the meeting layer, and the latter is error 002 of the SRTC layer; the two are unrelated.

<Tip>
  When troubleshooting, look at the first two digits first: if it starts with `2`, look for meeting-layer causes (permissions, meeting state, member roles); if it starts with `1`, look for audio and video layer causes (token, channel, network).
</Tip>

***

## Full error code tables by platform

[Web](/zh/meeting/web/types) (Chinese) · [Android](/en/meeting/android/error-codes) · [Windows](/zh/meeting/windows/error-codes) (Chinese) · [Swift](/en/meeting/swift/error-codes) · [iOS](/zh/meeting/ios/error-codes) (Chinese)

<Warning>
  Don't branch on the error **message text**—the text may change between versions, but error codes don't.
</Warning>