Livepeer Studio
Friday, August 21, 2020

How to Stream With Livepeer Video Service's RTMP API

Angie Ramirez
Angie Ramirez
5 min read
Streaming With Livepeer Video Services's RTMP API

Update: To learn how to stream with Livepeer Video Services using Postman, visit How to make API calls with Postman tutorial.

The RTMP API is the newest API feature from Livepeer Video Services. It allows a user to ingest RTMP streams into the Livepeer network, and receive a transcoded HLS output stream that enables adaptive bitrate streaming. RTMP, the Real-Time Messaging Protocol, and HLS, HTTP live streaming, are two of many standards for transporting video, audio, and data over the internet. In this tutorial, we'll go through the steps of creating and viewing transcoded streams with the RTMP feature of

Step 1: Create a free account with Livepeer Video Services, and generate an API key.

On, hit the Sign Up button at the top right of the homepage, enter your email and a password, wait for a verification email from Livepeer Video Services, click on the verify email button, and once signed into Livepeer Video Services, navigate to the API keys section of the site. Click the Create button to generate an API key, which should look something like this: d210eded-46a9-4119-86f9-64c33e003f1b. Be sure to record the API key once you generate it, as you won't be able to view it again after closing the window.

Step 2: Get a location-specific “base” URL

Depending on where you are in the world, you’ll need access to a different “ingest” and “playback” urls. This is important, because where your video enters the Livepeer network should be as close to where you are broadcasting from as possible to reduce latency. You’ll use this base URL to populate the “ingest base URL” and “playback base url” in step 4.

To get the base URL, curl You should see results similar to this:


Step 3: Create a stream

It’s time to create a stream, which will give us a couple of important fields: a "streamKey", a "playbackId", and an "id" (or a "streamId"). We’ll use all of these in steps 4 and 6.

To create a stream, send an HTTP POST request to In that request, include an Authorization header of Bearer YOUR_API_KEY, a JSON body with a stream name of your choosing, and details about which video profiles or renditions you’d like to transcode your stream into.

For example:

curl -X POST \-H 'content-type: application/json'\-H 'authorization: Bearer {api_key}'\-d '{ "name": "test_stream", "profiles": [ { "name": "720p", "bitrate": 2000000, "fps": 30, "width": 1280, "height": 720 }, { "name": "480p", "bitrate": 1000000, "fps": 30, "width": 854, "height": 480 }, { "name": "360p", "bitrate": 500000, "fps": 30, "width": 640, "height": 360 } ]}'\

The result from that HTTP POST request should look something like this:

{ "name": "test_stream", "profiles": [ { "name": "720p", "bitrate": 2000000, "fps": 30, "width": 1280, "height": 720 }, { "name": "480p", "bitrate": 1000000, "fps": 30, "width": 854, "height": 480 }, { "name": "360p", "bitrate": 500000, "fps": 30, "width": 640, "height": 360 } ], "id": "0bf161f3-95bd-4971-a7b1-4dcb5d39e78a", "createdAt": 1596081229373, "streamKey": "rlmn-uimq-jtgy-x98v", "playbackId": "emh3b2mxupongp5k" }

Step 4: Broadcast a stream

To broadcast a stream, you may use whatever capture device or software you’d like. We’ll use OBS for this example, video software that is available for free. Download here.

Once you’ve got OBS downloaded and open, go to "Settings", then select "Stream", and click on the "Service" dropdown to select "Custom".

To fill in the empty fields on that page, copy and past the “ingest” base URL from step 2 and copy into the “Server” or “Url” field. In this case, it’s rtmp:// For "Stream key", use "streamKey" from the newly created stream object in step 3. From our example, it’s rlmn-uimq-jtgy-x98v. Click "OK" to save the configuration.

Now go to "Settings" -> "Output", and hit “Output Mode” to “Advanced”. In the “Keyframe Interval” further down the page, type in "2". This will ensure a more consistent playback experience. Click "OK" to save the configuration. If you are building a live streaming application, you should help your users set their keyframe interval to 2 seconds as well.

When you click "Start Streaming", the RTMP stream will be pushed into the ingest point.

Step 5: Verify stream status

To verify a stream is running, you can fetch the stream status using the "id" of the stream object by sending a GET request to

For example:

curl -H 'authorization: Bearer {api_key}'\"{streamId}"

Your results will look like this:

{ "name": "test_stream", "profiles": [ { "bitrate": 2000000, "fps": 30, "height": 720, "name": "720p", "width": 1280 }, { "bitrate": 1000000, "fps": 30, "height": 480, "name": "480p", "width": 854 }, { "bitrate": 500000, "fps": 30, "height": 360, "name": "360p", "width": 640 } ], "id": "2d10f1fd-dbf7-495b-8aef-08916507fcce", "createdAt": 1596118509635, "lastSeen": 1596119750455 }

The "lastSeen" field represents when the stream was last observed by the monitoring system. It should contain an epoch that's close to the current time. To easily convert an epoch to a human-readable date, use this online calculator or take a look at this forum that might be helpful.

Step 6: Playback a live stream

Once the broadcast session is started, transcoding will automatically happen. Users can view the live stream with any HLS video player by using the playback URL:


From our example, the playback url should look like this:

Livepeer Video Services supports and has tested with video.js, hls.js, safari/ios native player, and Theoplayer. On safari, you can simply enter the playback URL into the address bar, and see your transcoded video come to life!

If you’d like to examine the playlist in more detail by using the playback URL, which should give you the full HLS playlist that includes all 4 different renditions, you may curl the URL for more information.

For example:

curl ""

You should see a response like this:


If you don't see a response like this, it's likely because the stream is not live. What we’re seeing here is rendition manifests, with file type information, the EXTM3U header, and information on individual renditions being returned, the EXT-X-STREAM-INF header.

For more information on streaming with the livepeer API, please visit our documentation page here.