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

> Values of the code field in server API responses

A `code` of `0` in the response body means success. Any other value means failure, and `msg` holds a human-readable error message.
**Check `code`**, not the `msg` text—messages may change between versions, codes don't.

## Business error codes

| Code | Name | Description |
| - | - | - |
| `2040` | CodeTokenChanged | This user has logged in elsewhere |
| `2041` | HeaderMissingAppId | Missing app\_id in request headers |
| `2042` | HeaderInvalidAppId | Invalid app\_id in request headers |
| `2043` | HeaderInvalidSignature | Invalid signature in request headers |
| `2044` | HeaderInvalidTimestamp | Device time is inaccurate. Correct the time and try again |
| `2045` | HeaderInvalidMeetSid | Invalid meet\_sid in request headers |
| `2046` | HeaderMissingNonce | Missing nonce in request headers |
| `2047` | HeaderMissingUserId | Missing user\_id in request headers |
| `2050` | MakeTokenFailed | Failed to generate token |
| `2051` | Unauthorized | Not authorized |
| `2052` | AuthorizationExpired | Authorization expired |
| `2053` | InvalidCallback | Invalid callback configuration |
| `2100` | MeetingError | Internal meeting error |
| `2101` | MeetingNotFound | Meeting does not exist |
| `2102` | MeetingNotStart | Meeting has not started |
| `2103` | MeetingEnded | Meeting has ended |
| `2104` | MeetingAlreadyShare | Someone is already sharing in the meeting |
| `2105` | MeetingNotSharing | No one is sharing in the meeting |
| `2106` | MeetingLocked | Meeting is locked |
| `2107` | MeetingKickout | Removed from the meeting; cannot enter again |
| `2108` | MemberInOther | Already in another meeting |
| `2109` | MemberInMeeting | Already in this meeting |
| `2110` | MemberNotInMeeting | Not in this meeting |
| `2111` | TargetNotInMeeting | Target is not in this meeting |
| `2112` | MicNotAllow | Not allowed to turn on the microphone |
| `2113` | CameraNotAllow | Not allowed to turn on the camera |
| `2114` | ChatNotAllow | Chat not allowed |
| `2115` | PasswordNotCorrect | Incorrect password |
| `2116` | MemberNotOnList | This meeting is for invitees only. Contact the host |
| `2117` | ShareNotAllow | Sharing not allowed |
| `2118` | EnterWaitingRoom | Could not enter the meeting; placed in the waiting room |
| `2120` | EnterBeforeHost | Cannot enter the meeting before the host |
| `2131` | CastCodeInvalid | Cast code is invalid or has expired |
| `2132` | CastToSelf | Cannot cast to your own device |

## Common framework error codes

Any API can return these. The most common is `10070`, returned when a parameter fails validation (required, length, character set, or value range); `msg` tells you which parameter.

| Code | Name | Description |
| - | - | - |
| `10000` | CodeUnSpecial | Unspecified error |
| `10001` | CodeDatabaseException | Database error |
| `10002` | CodeDataRecordNotFound | Record not found |
| `10003` | CodeDataRecordExists | Record already exists |
| `10040` | CodeUnAuthorized | Insufficient permissions |
| `10041` | CodeAuthFailed | Not logged in |
| `10042` | CodeTokenInvalid | Invalid token |
| `10043` | CodeTokenExpired | Token expired |
| `10051` | CodeNetError | Network error |
| `10055` | CodeRequestTimeout | Request timed out |
| `10070` | CodeInvalidParams | Invalid request parameters |