APIs are essential when it comes to software development. It allows software to communicate with each other to exchange information. In the beginning, when learning to make API calls, it can be a challenge using tools such as cURL in the terminal, FETCH in the frontend or backend option such as Express. Postman is a great tool for understanding the process of making API calls and getting feedback on the response of those calls. It provides a visual interface and allows developers to get a sense of the workflow which can provide easier transitions to using other tools such as cURL or Express.

In this tutorial, we will be using Postman to make API requests to Livepeer Video Services to get a better understanding on building an application similar to Twitch or YouTube. The Livepeer Video Services API consists of the standard features for users such as creating new live streams, recording the streams and getting a list of their streams. By leveraging Livepeer’s decentralized network for transcoding, it will be easier and cost effective to scale for in the future.

Step 1: Get access to Postman

Step 2: Get access to Livepeer Video Services

Now that we have access to these two services, let’s start interacting with them.

Step 3: Get anAPI key

With the API key, we will start going through the Stream section of Livepeer Video Services' API Reference. The reference uses the cURL command but we will do this using Postman instead.

To learn more about streaming Livepeer Video Services with the cURL command, visit the tutorial How To Stream With Livepeer Video Service’s RTMP API

Step 4:

Step 5: Create a stream

Now let’s get the stream we just created

Step 6: Retrieve a stream

Step 7: Get a list of streams

Step 8: Toggling a stream

Step 9: Update a stream

Step 10: Delete a stream

Now that you are able to use Postman to interact with Livepeer Video Services' API, take your skills to another level using cURL. To learn more, check out the tutorial How to Stream With Livepeer Video Service’s RTMP API.

How to Stream with RTMP API

First Published here