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

# Integration

> Add the Objective-C SRTC SDK (RTCEngineKit) to an iOS app: system requirements (iOS 16.0 since 3.1.0, no simulator, Bitcode off), manual framework integration with required system libraries and onnxruntime, or CocoaPods. Read before the iOS quickstart.

[RTCEngineKit](https://github.com/seastart/RTCEngineKit) offers two integration methods: you can integrate the SDK automatically with CocoaPods, or download the SDK manually and add it to your project.

* Language: Objective-C
* Build environment: Xcode 14.0 or later
* Supported OS: iOS 16.0 or later (since `3.1.0`; previously iOS 10.0)
* The SDK doesn't support building for the simulator
* Set Enable Bitcode to NO

<Warning>
  Starting with `3.1.0`, the SDK includes virtual background, and the minimum system requirement was raised from iOS 10.0 to **iOS 16.0**. Both `IPHONEOS_DEPLOYMENT_TARGET` in your project and `platform :ios` in your `Podfile` must be 16.0 or later; otherwise the dependency can't be resolved.
</Warning>

<Note>
  **There are two SRTC SDKs for Apple platforms—confirm which one you need first.** This page covers the Objective-C `RTCEngineKit`; there is also a native Swift SDK (`import SRTC`, distributed as a Swift Package, supporting both iOS and macOS)—see [Swift SDK](/en/rtc/swift/integration).

  **For new projects, we recommend the Swift SDK.** The two APIs can't be mixed, and don't include both in the same project.
</Note>

## Manual integration (not recommended)

* Get the version of [RTCEngineKit](https://github.com/seastart/RTCEngineKit) you need, then import the resulting `RTCEngineKit.framework` into your project.
* Add the system libraries that `RTCEngineKit` depends on

```objectivec theme={null}
VideoToolbox.framework
AudioToolbox.framework
AVFoundation.framework
CoreFoundation.framework
CoreMedia.framework
CoreVideo.framework
Foundation.framework
QuartzCore.framework
Metal.framework
CoreML.framework
MetalPerformanceShaders.framework
Security.framework
OpenGLES.framework
Accelerate.framework
CoreGraphics.framework
SystemConfiguration.framework
ReplayKit.framework
libc++.tbd
libiconv.tbd
libz.tbd
```

* Also add `onnxruntime.xcframework` (`1.24.x`). The inference engine for virtual background isn't bundled in `RTCEngineKit.framework`; the SDK keeps only its undefined symbols, which your app resolves at link time. Without this library, linking fails with undefined symbols such as `_OrtGetApiBase`. You can get the iOS package from [ONNX Runtime Releases](https://github.com/microsoft/onnxruntime/releases), or use the CocoaPods integration below, which brings it in automatically.

* Add `#import <RTCEngineKit/RTCEngineKit.h>` wherever you use `RTCEngineKit`

## Automatic integration (recommended)

Add `RTCEngineKit` to your `Podfile`

```objectivec theme={null}
pod 'RTCEngineKit'
```

Install

```objectivec theme={null}
pod install
```

If the library can't be found, try updating the local spec repo at the same time

```objectivec theme={null}
pod install --repo-update
```

If you can't install the latest SDK version, run the following command to update your local CocoaPods repo list

```objectivec theme={null}
pod repo update
```