Encrypted Compositions
This page 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, 2024.
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 feature is only available through Twilio Enterprise Edition or Security Edition. For further information contact the Twilio sales team.
Overview
The Twilio Composition Settings REST API lets you configure Twilio to store your compositions encrypted. Composition Settings work per-account (i.e. project). If you activate encryption, all Video Compositions in your account (or project) will get encrypted.
This document contains reference information about the Composition Settings REST API for encryption. For a step-by-step guide you can also read the Encrypting your Stored Media developer guide
Contents
URI Schemes
These are the URI schemes for the Composition Settings REST API and the supported methods:
/v1/CompositionSettings/DefaultGET: Retrieves current Composition Settings.POST: Updates the Composition Settings.
Composition Settings instance resource
The Default CompositionSettings resource holds the default composition settings for the given Twilio account (or project). Its configuration will be applied to all Recording Compositions created in such account (or project).
Base URL
The Compositions Settings default resource is located at the following Base URL:
https://video.twilio.com/v1/CompositionSettings/Default
Resource Properties
A CompositionSettings resource has the following properties:
| Resource Properties in REST API format | |
|---|---|
account_sid
|
The SID of the Account that created the CompositionSettings resource. |
friendly_name
|
The string that you assigned to describe the resource and that will be shown in the console |
aws_credentials_sid
|
The SID of the stored Credential resource. |
aws_s3_url
|
The URL of the AWS S3 bucket where the compositions are stored. We only support DNS-compliant URLs like |
aws_storage_enabled
|
Whether all compositions are written to the |
encryption_key_sid
|
The SID of the Public Key resource used for encryption. |
encryption_enabled
|
Whether all compositions are stored in an encrypted form. The default is |
url
|
The absolute URL of the resource. |
In the table above, the following properties are reserved for the feature called External S3 Storage:
aws_credentials_sidaws_s3_urlaws_storage_enabled
HTTP GET: Get Settings
Retrieves your account's default Composition Settings.
For example:
HTTP POST: Set Settings
Sets your account's default Composition Settings. POST requests support the following parameters:
| Parameters in REST API format | |
|---|---|
friendly_name
Required
|
A descriptive string that you create to describe the resource and show to the user in the console |
aws_credentials_sid
Optional
|
The SID of the stored Credential resource. |
encryption_key_sid
Optional
|
The SID of the Public Key resource to use for encryption. |
aws_s3_url
Optional
|
The URL of the AWS S3 bucket where the compositions should be stored. We only support DNS-compliant URLs like |
aws_storage_enabled
Optional
|
Whether all compositions should be written to the |
encryption_enabled
Optional
|
Whether all compositions should be stored in an encrypted form. The default is |
In the table above, the following parameters are reserved for the feature called External S3 Storage:
AwsCredentialsSidAwsS3UrlAwsStorageEnabled
Enabling Encrypted Compositions
The following code snippets illustrate how you can set Encryption in your Compositions settings:
Known Problems and Limitations
- No known problems.
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.
