Skip to main content
POST
Configure Azure Blob Storage

Overview

Set up Azure Blob Storage for uploaded videos. Authenticate with either an account key or a SAS token. Credentials are verified before saving.

Header Parameters

string
required
Your API key for authentication

Request Body

string
required
Azure Storage Account name
string
required
Blob container name
string
Storage Account access key (Base64 encoded). Required if sas_token is not provided.
string
SAS token for authentication. Required if account_key is not provided.
string
Optional folder prefix for organizing uploads (e.g., downloads/2024/)
string
default:"videos"
Base folder name for uploaded files. Defaults to videos if not specified. Set to a custom value to change the top-level folder where files are stored (e.g., downloads, media).
Provide at least one of account_key or sas_token. If both are supplied, the account key takes precedence.

Response

string
Success confirmation message
string
Storage provider type: blob
string
The configured container name
string
The configured folder prefix (if provided)

Examples

Success Response

Error Responses

Verification Process

When you submit storage configuration, Tornado:
  1. Validates that either account_key or sas_token is provided
  2. Creates a storage client with your credentials
  3. Attempts to upload a uniquely named small test object (tornado-verify-{uuid}.txt)
  4. Deletes the test file
  5. If successful, saves the configuration encrypted

Required SAS Permissions

When using a SAS token, ensure these permissions are enabled:
  • Read (r) - For downloading a delivered blob through the supplied SAS
  • Write (w) - For uploading files
  • Delete (d) - For cleanup operations
The validation probe writes and deletes its own object; it does not list the container. Read access is needed for delivery even though a successful write/delete probe alone does not prove it. A supplied SAS is reused in delivery URLs with its own permissions and expiry.