Twilio Live REST API
We are no longer allowing new customers to onboard to Twilio Live. Effective November 30, 2023, Twilio Live will End of Life. We have created this Migration Guide to help you identify an alternative solution for your use case.
The Twilio Live REST API allows you to create and manage livestreaming application resources from your back-end server via HTTPS requests. You can create and end PlayerStreamers, configure your MediaProcessor, and generate PlaybackGrants for Player SDK authentication.
All Twilio Live REST API resources use the following base URL.
https://media.twilio.com
All requests to the Twilio Live REST API are served over HTTPS. Unencrypted HTTP is not supported.
Authentication
HTTP requests to the REST API are protected with HTTP Basic authentication. To learn more about how Twilio handles authentication, please refer to our security documentation. You will use your Twilio API Key Sid as the username, and the key's associated API Key Secret as the password for HTTP Basic authentication.
curl -G https://media.twilio.com/v1/ \
-u '{API Key Sid}:{API Key Secret}'
You can manage your API Keys in the console.
Resources
The resources you will be interacting with via the Twilio Live REST API are:
| Resource | Description |
|---|---|
| PlayerStreamer | A PlayerStreamer is a resource that provides the ability to send livestream media content and to a Player SDK. |
| MediaProcessor | A MediaProcessor is a resource that provides the ability to capture audio and/or video from a web application. |
Need some help?
We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd by visiting Twilio's Stack Overflow Collective or browsing the Twilio tag on Stack Overflow.
