> ## 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 SRTC Swift SDK to an iOS or macOS app: system requirements (iOS 16 / macOS 14 since 1.4.0), Swift Package Manager setup in Package.swift or Xcode, when to use SRTCBroadcastKit, camera and microphone permissions, and a minimal integration checklist. Read before the Swift quickstart.
The SRTC Swift SDK is a native audio and video SDK distributed as a `Swift Package`, with the public module name `SRTC`. It currently supports:
* iOS 16.0 and later
* macOS 14.0 and later
* Xcode 15 and later
* Swift 5.9 and later
**Starting with `1.4.0`, the minimum system versions were raised from iOS 13 / macOS 10.15 to iOS 16 / macOS 14.** Projects below these minimums can't resolve version 1.4.0 or later (you get a dependency resolution failure, not a compile error); projects that still need to support older systems should stay on `1.3.3`.
The minimums are dictated by the inference runtime used for virtual background. SwiftPM's `platforms:` applies to the whole package and has no per-target minimum, so there's no way to apply this requirement to virtual background alone.
**There are two SRTC SDKs for Apple platforms—confirm which one you need first.** This section covers the native Swift SDK (`import SRTC`, distributed as a Swift Package, supporting both iOS and macOS); there is also an Objective-C `RTCEngineKit` (distributed via CocoaPods, iOS only)—see [iOS SDK](/zh/rtc/ios/integration) (Chinese).
**For new projects, we recommend the Swift SDK described here.** The two APIs can't be mixed, and don't include both in the same project.
***
### Integrate with Swift Package Manager
The SDK is distributed as a prebuilt XCFramework containing slices for three platforms: iOS devices, the iOS Simulator, and macOS.
#### Declare it in Package.swift
```swift theme={null}
// Package.swift
dependencies: [
.package(url: "https://github.com/seastart/srtc-swift-sdk.git", from: "1.4.5")
],
targets: [
.target(
name: "YourApp",
dependencies: [
.product(name: "SRTC", package: "srtc-swift-sdk")
]
)
]
```
#### Add it in Xcode
If you use an Xcode project instead of a pure SPM project:
* Open `File > Add Package Dependencies...`
* Enter `https://github.com/seastart/srtc-swift-sdk.git`
* Select `SRTC` for your target
#### SRTCBroadcastKit (only for full-screen screen sharing on iOS)
The same package also contains an `SRTCBroadcastKit` product. It is used only by the Broadcast Upload Extension for iOS screen sharing;
regular integrations don't need it. For integration steps, see [Screen sharing](/zh/rtc/swift/advanced/screen-sharing) (Chinese).
Add `SRTCBroadcastKit` only to the extension target—**don't** add it to the app target; the extension target also must **not**
depend on `SRTC`. The extension process has a 50 MB memory limit, and linking WebRTC gets it killed by the system; meanwhile, `SRTC` on the app side already
contains the same code, and linking it twice puts two copies of the same types in one process.
***
### Import the SDK
```swift theme={null}
import SRTC
```
The underlying WebRTC and signaling components are resolved automatically by Swift Package Manager; you don't need to add another layer manually.
***
### Configure permissions
#### iOS
Add the following to `Info.plist`:
```xml theme={null}
NSCameraUsageDescription
Camera access is required for video calls
NSMicrophoneUsageDescription
Microphone access is required for voice calls
```
#### macOS
The app's `Info.plist` also needs:
```xml theme={null}
NSCameraUsageDescription
Camera access is required for video calls
NSMicrophoneUsageDescription
Microphone access is required for voice calls
```
If you use screen sharing, also note:
* macOS screen sharing is based on `ScreenCaptureKit`
* Sharing a window or display requires the user to grant permission in a system prompt
* Capturing system audio requires newer system capabilities—see [Screen sharing](/zh/rtc/swift/advanced/screen-sharing) (Chinese)
***
### Minimal integration checklist
* `SRTC` has been added to your target's dependencies
* Camera / microphone permission strings are configured
* Your backend can already issue the token needed to join a channel
* Your UI has a local preview area and a remote video area ready
After completing the steps above, continue with [Quickstart](/en/rtc/swift/quickstart).