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

# Sign-in and roll call

> Run in-meeting sign-in with the SMeeting Swift SDK: the host starts and ends timed sign-in rounds, members sign in, and you query counts and lists; plus receiving roll call events and answering them with the right ID. Read when adding attendance features to a meeting.

### Sign-in

Sign-in is a timed activity: the host starts it, members tap to sign in within the time limit, and the host can view the statistics and the list at any time. Activities are distinguished by `epoch` (round), and a meeting can run multiple rounds.

#### Start and end

```swift theme={null}
// Start a sign-in round
// dur is in minutes; here it's 30 minutes
try await meeting.signInCreate(dur: 30, desc: "Morning session sign-in")

// End the current round early
try await meeting.signInFinish()
```

`dur` is the duration of the sign-in activity, **in minutes**; the actual start and end times of the activity are given by `beginAt` / `endAt` in the events and lists below.

#### Members sign in

```swift theme={null}
try await meeting.signInSign()
```

#### Query

```swift theme={null}
// All sign-in activities of this meeting; now is the server's current time, which you can use to compute the remaining countdown
let (list, now) = try await meeting.signInList()

// Number of members signed in for a round
let count = try await meeting.signInCount(epoch: epoch)

// Sign-in list of a round, optionally filtered by nickname
let details = try await meeting.signInDetail(epoch: epoch, nickname: nil)
```

`SignInfo` fields: `uid` (initiator), `beginAt`, `dur`, `endAt`, `desc`, `nums` (number signed in).
`SignDetailInfo` fields: `id`, `epoch`, `nickname`, `role`, `userId`, `createdAt`.

#### Sign-in events

```swift theme={null}
func meeting(_ meeting: SMeetingEngine, signInActivity data: SignInActivityEventData) {
    // data.hostId / data.hostName initiator
    // data.epoch  round
    // data.beginAt / data.dur / data.endAt start, end, and duration
    // data.desc   sign-in description
}

func meeting(_ meeting: SMeetingEngine, signInDidFinish data: SignInFinishEventData) {
    // data.hostId / data.hostName / data.epoch
}
```

A typical approach: when you receive `signInActivity`, show a sign-in button with a countdown to `endAt`; when you receive `signInDidFinish`, hide it.

***

### Roll call

When you're called in a roll call, you receive an event:

```swift theme={null}
func meeting(_ meeting: SMeetingEngine, rollCallNamed data: RollCallNamedEventData) {
    // data.id   identifier of this member in the roll call record; pass it back as-is when answering
    // data.sid  uid of the host who started this roll call
    // data.time server's current time
}
```

To answer, **pass the event's `id` straight back**:

```swift theme={null}
func meeting(_ meeting: SMeetingEngine, rollCallNamed data: RollCallNamedEventData) {
    Task {
        try await meeting.rollCallAnswer(rollCallUserId: data.id)
    }
}
```

<Warning>
  Don't use `data.sid` as the parameter—it's the uid of the host who started the roll call, not the roll call record identifier.
</Warning>

> The Swift SDK currently provides only the member-side ability to answer a roll call. Starting a roll call and querying roll call details are host-side flows that must be done through the server API.
>
> Roll call also requires the feature to be deployed on the server; in environments where it isn't enabled, calls return an "endpoint not found" error.

***

### Related pages

* [Host controls](/en/meeting/swift/advanced/host-controls)
* [Events](/en/meeting/swift/events)