Simple Encoding API - Live


What is this?

This is just a port from our article:

Just to showcase the difference to an existing documentation.


Simple Live Encoding Jobs are quick and easy way to transcode your RTMP or SRT Input into a best practise bitrate ladder for efficient and high-quality using DASH/HLS delivery to your audience . All you need is a single API call that provides the input type you want to use, and output destination details where to store the encoded live content.


  1. Encoder Version: STABLE
  2. SDK Version: v 1.106.0 or higher
  3. Input: SRT or RTMP (push only)

Supported Features

  • Input Sources: RTMP, SRT
  • Output Destinations: AWS S3, Google Cloud Storage (GCS), Azure Blob Storage (ABS), Akamai NetStorage
    • Output Characteristics:
      • At least one Output Destination
      • Video: H264, segmented fMP4, fixed rendition ladder (240p, 360p, 480p, 720p, 1080p)
      • Audio: AAC, segmented fMP4, one audio rendition only
      • Highest Resolution selectable (SD = up to 480p, HD up to 720p, FULL_HD up to 1080p)
      • Manifests: DASH/HLS


A Simple Live Encoding Job is defined by an

  • An input source
  • An output destination
  • A cloud region.

that’s it! :)

Once a Simple Encoding Job is started, the template is converted into an actual Encoding, adapted to the input and output definition.

Job lifecycle

After starting the Simple Live Encoding Job, it goes through the following stages:

  • CREATED: Job has been created is waiting to be started.
  • EXECUTING: Job is currently being executed and creating an Live Encoding
  • FAILURE: Job could not create an Live Encoding, errors property for more information
  • RUNNING: Job created an Live Encoding. At this time, an encoding-ID is available and the Live Encoding itself is either in state QUEUED or RUNNING and provides the details needed to configure an input source (e.g. OBS Studio, hardware encoders, etc) to push their signal to the Live Encoding.
  • FINISHED: The Encoding created by this job finished successfully
  • ERROR: The Encoding created by this job failed, errors property for more information
  • CANCELED: The Encoding has been started but has been canceled manually by the user.

You can retrieve status information with the Job details endpoint

Note that the Encoding created and managed by the Job has its own statuses, documented in this FAQ, and queried through the Encoding Status endpoint.

Create a Simple Live Encoding Job


The simplest way to create a simple encoding is a plain HTTP POST request sent to the Bitmovin API or try it with this Postman Collection.

curl --location --request POST '' \
--header 'x-api-key: YOUR_BITMOVIN_API_KEY' \
--header 'Content-Type: application/json' \
--data-raw '{
    "cloudRegion": "EUROPE",
    "input": {
        "inputType": "RTMP",
        "inputAspectRatio": "WIDE_16_9"
    "outputs": [
            "url": "s3://yourbucket/path/to/your/live-folder/{uuid}/",
            "credentials": {
                "accessKey": "S3_OUTPUT_ACCESS_KEY",
                "secretKey": "S3_OUTPUT_SECRET_KEY"
            "makePublic": true,
            "maxResolution": "FULL_HD"

Bitmovin OpenAPI SDK

Beyond a plain HTTP POST, you can use any of the Bitmovin SDKs to start your job. The following code sample is the equivalent of the REST API call above, but using the Bitmovin OpenAPI Java SDK.

var input = new SimpleEncodingLiveJobInput();
//input.setInputAspectRatio(SimpleEncodingLiveInputAspectRatio.WIDE_16_9) //default aspect ratio

var outputCredentials = new SimpleEncodingVodJobAccessKeyCredentials();

var output = new SimpleEncodingLiveJobUrlOutput();

SimpleEncodingLiveJobRequest job = new SimpleEncodingLiveJobRequest();

var jobResponse =;
do {
  jobResponse =;
} while (jobResponse.getStatus() != SimpleEncodingLiveJobStatus.RUNNING);

//Stop the Live Encoding;

Cloud Region

A list of all available cloudRegion values can be found in our API-Reference.



The URL you will have to enter into the configuration of your RTMP Encoder looks like:

Both values become available as soon as the Live Encoding is in status RUNNING. They can be obtained either

  • by viewing the details of the Live Encoding in the Bitmovin dashboard, or
  • by querying the details of the Simple Live Encoding Job from the API, and extracting its externalIp and streamKey property.


The URL you will have to enter into the configuration of your SRT Encoder looks like:

The External_IP for the Live Encoding Ingest Endpoint becomes available as soon as the Live Encoding is in status RUNNING.

  • by viewing the details of an Live Encoding in the Bitmovin dashboard, or
  • by querying the details of the Live Encoding directly from the API


In order to ensure that the output path is unique for all your Live Encodings, and avoid files being overriden, we recommend that you add a {uuid} placeholder in the path, which will be replaced with a unique identifier at run-time.

Folder Structure

Simple Encoding Jobs will create the following folder structure at the given destination. The output files can be found in the following locations on every configured output:


  • video/{width}x{height}/ (multiple subfolders containing different output renditions)
  • audio/ (folder containing audio output files)
  • index.m3u8 (HLS manifest file)
  • stream.mpd (DASH manifest file)


  • s3://<my-bucket>/path/to/live/{uuid}/

Credentials for S3 URLs are mandatory and can be provided via AWS access/secret keys or role-based authentication. Generic S3 is currently not supported.

AWS Access/Secret Keys

var keyCredentials = new SimpleEncodingVodJobAccessKeyCredentials();

var output = new SimpleEncodingLiveJobUrlOutput();


var roleBasedCredentials = new SimpleEncodingVodJobS3RoleBasedCredentials();

var output = new SimpleEncodingLiveJobUrlOutput();

useExternalId (default: false) is an optional property and controls if the customer’s orgId should be used as externalId when assuming the AWS role, or not. Its an additional security measure to prevent unauthorized users assume a role by obtaining the role ARN somehow. For more details, please see S3 Role-Based Input for details about the externalId, and be aware that the simple encoding API only supports the externalIdMode GLOBAL.

Google Cloud Storage (GCS)

  • gcs://<my-bucket>/path/to/live/{uuid}/

Credentials for GCS URLs are mandatory and can be provided as HMAC keys or a service account.


var keyCredentials = new SimpleEncodingVodJobAccessKeyCredentials();

var output = new SimpleEncodingLiveJobUrlOutput();


Note that the service credentials provided in the following snippet are just for example. You need to obtain your service credentials from your GCP account.

var serviceAccountCredentials = new SimpleEncodingVodJobGcsServiceAccountCredentials();
    + "    \"type\": \"service_account\",\n"
    + "    \"project_id\": \"bitmovin\",\n"
    + "    \"private_key_id\": \"abcdefghijklmnopqrstuvwxyz\",\n"
    + "    \"private_key\": \"-----BEGIN PRIVATE KEY-----\\nOwdXyjRT9F4A==\\n-----END PRIVATE KEY-----\\n\",\n"
    + "    \"client_email\": \"[email protected]\",\n"
    + "    \"client_id\": \"10440564562784234997\",\n"
    + "    \"auth_uri\": \"\",\n"
    + "    \"token_uri\": \"\",\n"
    + "    \"auth_provider_x509_cert_url\": \"\",\n"
    + "    \"client_x509_cert_url\": \"\"\n"
    + "}");

var output = new SimpleEncodingLiveJobUrlOutput();

Azure Blob Storage

  • https://<account><container>/path/to/live/{uuid}/

Credentials for Azure Blob Storage URLs are mandatory and can be provided via the storage account accesss key credentials.

var azureCredentials = new SimpleEncodingVodJobAzureCredentials();

var output = new SimpleEncodingLiveJobUrlOutput();

Akamai NetStorage

  • https://<host><CP-code>/path/to/live/{uuid}/

Credentials for Akamai NetStorage URLs are mandatory and can be provided via username and password

var authenticationCredentials = new SimpleEncodingVodJobUsernamePasswordCredentials();

var output = new SimpleEncodingLiveJobUrlOutput();

Known Limitations

  • DRM Protection is not available.
  • Audio
    • Only the first audio track is extracted from an input file
    • The Output Channel Layout is going to be STEREO (2.0), regardless of what is provided by the input stream.
  • Webhooks: Once a Simple Live Encoding Job is successfully started, standard generic Live Encoding webhooks can be used to track the progress of the live encoding.

Did this page help you?