Authorization

You'll need to authenticate your requests to access any of the endpoints in the Streaming Availability API. In this guide, we'll look at how authentication works.

API Key

To authorize your requests, you need to include a valid API key in your requests.

Streaming Availability API uses RapidAPI Platform to manage API keys.

With their own words, "RapidAPI is the world's largest API hub, is used by over three million developers to find, test, and connect to thousands of APIs — all with a single API key and dashboard."

Generating an API key is through RapidAPI is a simple process and does not require any payment information until you decide to upgrade to a paid plan.

Step 1: Sign Up

If you don't have a RapidAPI account, you'll need to sign up for one. You can do so by visiting the RapidAPI's Sign Up Page.

Step 2: Subscribe to Streaming Availability API

Once you create your account, you can subscribe to the Streaming Availability API by visiting the Streaming Availability API's Pricing Page on RapidAPI.

Simply choose the plan that fits your needs and click the "Subscribe" button. Since the version 3, all the plans, including the free one, support all the available features/endpoints. Only difference is the number of requests you can make per month.

Step 3: Get Your API Key

Once you subscribe to the API, you can get your API key by visiting the Streaming Availability API's Page.

Image showing the location of API key on the Streaming Availability API's RapidAPI page

Or you can visit the RapidAPI's Developer Dashboard Page and click on the "Authorization" tab.

Image showing the location of API key on the RapidAPI Developer Dashboard

You can now use this API key to authenticate your requests to the Streaming Availability API. If you are sending the requests manually, you can include the API key in the X-RapidAPI-Key header. If you are using one of the official client libraries, you can set the API key in the client's configuration, and the client library will take care of the rest.

Make sure to keep your API key secure and do not expose it in public repositories or client-side code.

Was this page helpful?