This documentation is for reference only. We are no longer onboarding new customers to Programmable Video. Existing customers can continue to use the product until December 5, 2026.
We recommend migrating your application to the API provided by our preferred video partner, Zoom. We've prepared this migration guide to assist you in minimizing any service disruption.
This guide provides you with an overview of the key objects you'll use in the Programmable Video API to build your video application with the Twilio Programmable Video iOS SDK.
Note: If you haven't already done so, take a look at the open source video collaboration app and quickstart apps. Then come back to this guide for more detail on how to add video to your own app.
If you've worked with WebRTC in the past, you'll find that Programmable Video provides a simple wrapper around WebRTC's lower-level APIs to make it easy to build rich audio and video applications. You can still access lower-level primitives, but that's not required to get started.
Additionally, Programmable Video provides the missing pieces required to use WebRTC to build sophisticated applications: Global STUN/TURN relays, media services for large-scale group conferences and recording, and signaling infrastructure are all included.
Let's start with an overview of the Programmable Video API:
Room
represents a real-time audio, video, and/or screen-share session, and is the basic building block for a Programmable Video application.
Peer-to-peer Room
, media flows directly between participants. Supports up to 10 participants in a mesh topology.
Group Room
, media is routed through Twilio's Media Servers.
Supports up to 50 participants.
Participants
represent client applications that are connected to a Room and sharing audio and/or video media with one another.
Tracks
represent the individual audio and video media streams that are shared within a Room.
LocalTracks
represent the audio and video captured from the local microphone and camera.
RemoteTracks
represent the audio and video tracks from other participants connected to the Room.
The following code samples illustrate common tasks that you as a developer may wish to perform related to a Room and its Participants.
To start using the iOS Programmable Video SDK in your apps, you need to perform a few basic tasks first.
The Twilio Video iOS SDK dynamic framework can be installed using Swift Package Manager, CocoaPods or manually, as you prefer.
You can add Programmable Video for iOS by adding the https://github.com/twilio/twilio-video-ios
repository as a Swift Package.
In your Build Settings, you will also need to modify Other Linker Flags
to include -ObjC
.
As of the latest release of Xcode, there is a known issue with consuming binary frameworks distributed via Swift Package Manager. The current workaround to this issue is to add a Run Script Phase
to the Build Phases
of your Xcode project. This Run Script Phase
should come after the Embed Frameworks
build phase. This new Run Script Phase
should contain the following code:
_10find "${CODESIGNING_FOLDER_PATH}" -name '*.framework' -print0 | while read -d $'\0' framework_10do_10 codesign --force --deep --sign "${EXPANDED_CODE_SIGN_IDENTITY}" --preserve-metadata=identifier,entitlements --timestamp=none "${framework}"_10done
_10source 'https://github.com/CocoaPods/Specs'_10_10platform :ios, '12.2'_10_10target 'TARGET_NAME' do_10 pod 'TwilioVideo', '~> 5'_10end
Then run pod install
to install the dependencies to your project.
TwilioVideo.xcframework
is distributed as a dynamic iOS framework that you can drag and drop into your existing projects.
View all Video iOS Releases here or just download the latest Video dynamic framework here.
Once you've downloaded and unpacked the XCFramework, navigate to your Xcode project's General settings page. Drag and drop TwilioVideo.xcframework
onto the Frameworks, Libraries, and Embedded Content section. Ensure that "Copy items if needed" is checked and press Finish. Ensure that "Embed & Sign" is selected.
In your Build Settings, you will also need to modify Other Linker Flags
to include -ObjC
.
To allow a connection to a Room to be persisted while an application is running in the background, you must select the Audio, AirPlay, and Picture in Picture
background mode from the Capabilities
project settings page.
Twilio Video requires user permission for features like sharing video from the camera or audio from the microphone. Consider how your applications might function with reduced functionality in case some permissions (like the camera) are declined.
Friendly Name | Privacy Usage Description Key | iOS Version | Recommendation | |
---|---|---|---|---|
Camera | NSCameraUsageDescription | All | Request permissions using AVCaptureDevice.requestAccess(for:completionHandler:) before calling TwilioVideoSDK.connect(options:delegate:) with a TVICameraSource. | |
Microphone | NSMicrophoneUsageDescription | All | Request permissions using AVAudioSession.requestRecordPermission() before calling TwilioVideoSDK.connect(options:delegate:) when Participants publish or subscribe to audio tracks with TVIDefaultAudioDevice. (*) | |
Local Network | NSLocalNetworkUsageDescription | 14.0 + | This permission is not recommended unless your app is already using NWConnection APIs on the local network. Twilio Video only requests permissions after you connect to a Peer-to-Peer Room with TVILocalNetworkPrivacyPolicyAllowAll on iOS 14. |
The iOS SDK supports iOS 12.2 or higher. It is built for arm64 and x86_64 architectures with Bitcode slices for arm64 devices.
The TwilioVideo.framework
is built with Xcode 13. The framework can be consumed with previous versions of Xcode. However, re-compiling Bitcode when exporting for Ad Hoc or Enterprise distribution requires the use of Xcode 13.x.
API Keys represent credentials to access the Twilio API. They are used for two purposes:
For the purposes of this guide, we will create our API Key from the Twilio Console.
To execute the code samples below, you'll need to generate an Access Token. An Access Token is a short-lived credential used to authenticate your client-side application to Twilio.
You can generate an Access Token using either the Twilio CLI or a Twilio helper library. For application testing purposes, the Twilio CLI provides a quick way to generate Access Tokens that you can then copy/paste into your application.
To use the CLI, you will need to install the Twilio CLI and log in to your Twilio account from the command line; see the CLI Quickstart for instructions. Then, you can install the Token CLI plugin with the following command:
_10twilio plugins:install @twilio-labs/plugin-token
To generate an Access Token, run the following command. --identity
is a required argument and should be a string that represents the user identity for this Access Token.
_10twilio token:video --identity=<identity>
In a production application, your back-end server will need to generate an Access Token for every user in your application. Visit the User Identity and Access Token guide to learn more. You can find examples of how to generate an Access Token for a participant using Twilio's helper libraries in the User Identity and Access Token guide.
Call TwilioVideo.connect()
to connect to a Room from your iOS application. Once connected, you can send and receive audio and video streams with other Participants who are connected to the Room.
_19@IBAction func createARoom(sender: AnyObject) {_19 let connectOptions = ConnectOptions(token: accessToken) { (builder) in_19 builder.roomName = "my-room"_19 }_19 room = TwilioVideoSDK.connect(options: connectOptions, delegate: self)_19}_19_19// MARK: RoomDelegate_19_19func roomDidConnect(room: Room) {_19 print("Did connect to Room")_19_19 if let localParticipant = room.localParticipant {_19 print("Local identity \(localParticipant.identity)")_19_19 // Set the delegate of the local particiant to receive callbacks_19 localParticipant.delegate = self_19 }_19}
You must pass the Access Token when connecting to a Room. You may also optionally pass the following:
The name of the Room specifies which Room you wish to join. If a Room by that name does not already exist, it will be created upon connection. If a Room by that name is already active, you'll be connected to the Room and receive notifications from any other Participants also connected to the same Room. Room names must be unique within an account.
You can also create a Room using the Rooms REST API. Look at the REST API Rooms resource docs for more details.
Example: Create a Room called DailyStandup
_10 curl -XPOST 'https://video.twilio.com/v1/Rooms' \_10 -u '{API Key SID}:{API Secret}' \_10 -d 'UniqueName=DailyStandup'
Note: If you don't specify a Type attribute, then Twilio will create a Group Room by default.
You can also set the room type from the Room Settings page in the Twilio Video Console. Twilio will use the room type set on Room Settings page, when you create a room from the client-side or the REST API.
Note: Twilio will set the Room Type as Group by default on the Room Settings page.
Once a Room is created, Twilio will fire a room-created
webhook event, if the StatusCallback URL is set. You can set the StatusCallback URL on the Room Settings page, if you want create a room from the client-side.
If you create a room using the REST API, then you need to provide a StatusCallback URL while creating the room.
_10 curl -XPOST 'https://video.twilio.com/v1/Rooms' \_10 -u '{API Key SID}:{API Secret}' \_10 -d 'UniqueName=DailyStandup' \_10 -d 'StatusCallback=https://hooks.yoursite.com/room-events' \_10 -d 'StatusCallbackMethod=POST' \_10 -d 'Type=group'
Recordings can be enabled only on Group Rooms. Set Recordings to Enabled
to record participants when they connect to a Group Room.
Recordings can also be enabled on Group Rooms through via the Rest API at Room creation time by setting the RecordParticipantsOnConnect
property to true
.
_10curl -XPOST 'https://video.twilio.com/v1/Rooms' \_10-u '{API Key SID}:{API Secret}' \_10-d 'UniqueName=DailyStandup' \_10-d 'Type=group' \_10-d 'RecordParticipantsOnConnect=true' \_10-d 'StatusCallback=http://example.org'
If you'd like to join a Room you know already exists, you handle that exactly the same way as creating a room: just pass the Room name to the connect
method.
Once in a Room, you'll receive a room:participantDidConnect:
callback for each Participant that successfully joins. Querying the remoteParticipants
getter will return any existing Participants who have already joined the Room.
_19@IBAction func joinRoom(sender: AnyObject) {_19 let connectOptions = ConnectOptions(token: accessToken) { (builder) in_19 builder.roomName = "existing-room"_19 })_19 room = TwilioVideoSDK.connect(options: connectOptions, delegate: self)_19}_19_19// MARK: RoomDelegate_19_19func roomDidConnect(room: Room) {_19 print("Did connect to room")_19_19 if let localParticipant = room.localParticipant {_19 print("Local identity \(localParticipant.identity)")_19_19 // Set the delegate of the local particiant to receive callbacks_19 localParticipant.delegate = self_19 }_19}
You can capture local media from your device's microphone, camera or screen-share on different platforms in the following ways:
In an iOS application, begin capturing audio data by creating a TVILocalAudioTrack
, and begin capturing video by creating a TVILocalVideoTrack
with an associated TVIVideoCapturer
. The iOS Video SDK provides customizable video capturers for both camera and screen capture.
_13// Create an audio track_13var localAudioTrack = LocalAudioTrack()_13_13// Create a data track_13var localDataTrack = LocalDataTrack()_13_13// Create a CameraSource to provide content for the video track_13var localVideoTrack : LocalVideoTrack?_13_13// Create a video track with the capturer._13if let camera = CameraSource(delegate: self) {_13 localVideoTrack = LocalVideoTrack(source: camera)_13}
When the client joins a Room, the client can specify which Tracks they wish to share with other Participants. Imagine we want to share the audio and video Tracks we created earlier.
_15let connectOptions = ConnectOptions(token: accessToken) { (builder) in_15 builder.roomName = "my-room"_15_15 if let audioTrack = localAudioTrack {_15 builder.audioTracks = [ audioTrack ]_15 }_15 if let dataTrack = localDataTrack {_15 builder.dataTracks = [ dataTrack ]_15 }_15 if let videoTrack = localVideoTrack {_15 builder.videoTracks = [ videoTrack ]_15 }_15}_15_15var room = TwilioVideoSDK.connect(options: connectOptions, delegate: self)
For some use cases (such as a ReplayKit broadcast extension) you may wish to connect as a publish-only Participant that is not subscribed to any Tracks. If you are connecting to a Group Room, you may disable automatic subscription behavior via ConnectOptions.
_10let connectOptions = ConnectOptions(token: accessToken) { (builder) in_10 builder.isAutomaticSubscriptionEnabled = false_10 builder.roomName = "my-room"_10_10 if let audioTrack = localAudioTrack {_10 builder.audioTracks = [ audioTrack ]_10 }_10}_10_10var room = TwilioVideo.connect(options: connectOptions, delegate: self)
When you join a Room, Participants may already be present. You can check for existing Participants in the roomDidConnect:
callback by using the remoteParticipants
getter. To receive RemoteParticipantDelegate
callbacks you will need to set the RemoteParticipant.delegate
property for each connected Remote Participant.
_32room = TwilioVideo.connect(options: connectOptions, delegate: self)_32_32// MARK: RoomDelegate_32_32func roomDidConnect(room: Room) {_32 // The Local Participant_32 if let localParticipant = room.localParticipant {_32 print("Local identity \(localParticipant.identity)")_32_32 // Set the delegate of the local participant to receive callbacks_32 localParticipant.delegate = self_32 }_32_32 // Connected participants already in the room_32 print("Number of connected Participants \(room.remoteParticipants.count)")_32_32 // Set the delegate of the remote participants to receive callbacks_32 for remoteParticipant in room.remoteParticipants {_32 remoteParticipant.delegate = self_32 }_32}_32_32func participantDidConnect(room: Room, participant: RemoteParticipant) {_32 print ("Participant \(participant.identity) has joined Room \(room.name)")_32_32 // Set the delegate of the remote participant to receive callbacks_32 participant.delegate = self_32}_32_32func participantDidDisconnect(room: Room, participant: RemoteParticipant) {_32 print ("Participant \(participant.identity) has left Room \(room.name)")_32}
When Participants connect to or disconnect from a Room that you're connected to, you'll be notified via an event listener: Similar to Room Events, Twilio will fire Participant events if the StatusCallback webhook URL is set when the Room is created. These events help your application keep track of the participants who join or leave a Room.
_10// MARK: RoomDelegate_10_10// First, we set a Participant Delegate when a Participant first connects:_10func participantDidConnect(room: Room, participant: RemoteParticipant) {_10 print("Participant connected: \(participant.identity)")_10 participant.delegate = self_10}
To see the Video Tracks being sent by remote Participants, we need to render them to the screen:
_28// MARK: RemoteParticipantDelegate_28_28/*_28 * In the Participant Delegate, we can respond when the Participant adds a Video_28 * Track by rendering it on screen._28 */_28func didSubscribeToVideoTrack(videoTrack: RemoteVideoTrack,_28 publication: RemoteVideoTrackPublication,_28 participant: RemoteParticipant) {_28_28 print("Participant \(participant.identity) added a video track.")_28_28 if let remoteView = VideoView.init(frame: self.view.bounds,_28 delegate:self) {_28_28 videoTrack.addRenderer(remoteView)_28 self.view.addSubview(remoteView)_28 self.remoteView = remoteView_28 }_28}_28_28// MARK: VideoViewDelegate_28_28// Lastly, we can subscribe to important events on the VideoView_28func videoViewDimensionsDidChange(view: VideoView, dimensions: CMVideoDimensions) {_28 print("The dimensions of the video track changed to: \(dimensions.width)x\(dimensions.height)")_28 self.view.setNeedsLayout()_28}
Sometimes you need to make sure you're looking fantastic before entering a Room. We get it. The iOS SDK provides a means to render a local camera preview outside the context of an active Room:
_23// Use CameraSource to produce video from the device's front camera._23_23if let camera = CameraSource(delegate: self),_23 let videoTrack = LocalVideoTrack(source: camera) {_23_23 // VideoView is a VideoRenderer and can be added to any VideoTrack._23 let renderer = VideoView(frame: view.bounds)_23}_23if let camera = TVICameraCapturer(source: .frontCamera),_23 let videoTrack = TVILocalVideoTrack(capturer: camera) {_23_23 // TVIVideoView is a TVIVideoRenderer and can be added to any TVIVideoTrack._23 let renderer = TVIVideoView(frame: view.bounds)_23_23 // Add renderer to the video track_23 videoTrack.addRenderer(renderer)_23_23 self.localVideoTrack = videoTrack_23 self.camera = camera_23 self.view.addSubview(renderer)_23} else {_23 print("Couldn't create CameraCapturer or LocalVideoTrack")_23}
You can disconnect from a Room you're currently participating in. Other Participants will receive a participantDisconnected
event.
_10// To disconnect from a Room, we call:_10room?.disconnect()_10_10// This results in a callback to RoomDelegate#roomDidDisconnect(room: Room, error: Error?)_10_10// MARK: RoomDelegate_10_10func roomDidDisconnect(room: Room, error: Error?) {_10 print("Disconnected from room \(room.name)")_10}
The Video SDK will raise notifications when a Room is reconnecting due to a network disruption. A Room reconnection is triggered due to a signaling or media reconnection event. To capture when a reconnection is triggered or that it has reconnected:
_10// MARK: RoomDelegate_10_10// Error will be either TwilioVideoSDK.Error.signalingConnectionError or TwilioVideoSDK.Error.mediaConnectionError_10func roomIsReconnecting(room: Room, error: Error) {_10 print("Reconnecting to room \(room.name), error = \(String(describing: error))")_10}_10_10func roomDidReconnect(room: Room) {_10 print("Reconnected to room \(room.name)")_10}
In a Peer-to-Peer Room, each Participant has media connections to all the other Participants in the Room. If all media connections between the LocalParticipant and all other Participants are broken, then the LocalParticipant's Room will enter the reconnecting state until media connectivity with at least one Participant is re-established.
There are certain instances when an application is put into the background that both the signaling and media connection are closed, which will cause the reconnecting delegate method to be invoked:
The Programmable Video REST API
allows you to control your video applications from your back-end server via HTTP requests. To learn more check out the Programmable Video REST API docs.
We love feedback and questions especially those with helpful debugging information so we can diagnose and respond quickly. When submitting issues or support tickets, it would be great if you add the following:
After gathering the above information, you can get help in a few ways:
For issues related to the Twilio Video iOS SDK itself:
For issues related to the Twilio Video iOS Quickstarts:
To enable debug level logging, add the following code in your application:
_10TwilioVideoSDK.setLogLevel(.debug)