Access Tokens

In this video we show you, how to create and use access tokens to access the API.

In the dynamic landscape of digital services and content delivery, seamless integration and secure communication are paramount. For businesses utilizing RapidStream’s services, understanding the intricacies of access tokens is key to unlocking the full potential of their backend processes. In this guide, we’ll walk you through the steps of creating and managing access tokens, enabling you to interact with RapidStream’s services through API calls.

Creating an Access Token:

To begin harnessing the power of RapidStream’s backend services, you must first create an access token. This token acts as a secure key, allowing your backend processes to communicate with RapidStream’s APIs. Follow these steps to generate an access token tailored to your specific needs:

  1. Access Token Scope: Identify the functionalities you require by selecting the appropriate scope.

    • updateCatalog: Enables you to send your EPG catalog with metadata relevant for ad servers.
    • requestAdBreak: Facilitates the request for ads for your ad break.
  2. Token Information: Provide a name for your access token to easily recognize it in your overview.

  3. Token Expiration (Optional): Optionally, set an expiration date for the access token to enhance security. If not specified, the token will remain valid until revoked.

  4. Token Generation: After entering the necessary details, the access token will be generated and presented to you. Note that this value is unique and begins with rs_at-, followed by 30 alpha-numeric characters. Keep this token secure, as it is intended for backend usage only.

Managing Access Tokens:

Once you have your access token, you can seamlessly integrate it into your backend processes. It’s important to be aware of a few key points:

  • One-Time Presentation: The access token is presented to you only once during creation. Ensure you securely store it for future use.

  • Revocation: You have the flexibility to revoke an access token at any time. Upon revocation, API requests using the invalidated token will receive a 401 status code with the following response body:

	"type": "unauthorized",
	"title": "Bad request",
	"detail": "unauthorized",
	"status": 401

By following these guidelines, you can seamlessly integrate RapidStream’s services into your backend processes, ensuring secure and efficient communication. Remember to handle access tokens with care, keeping them confidential and revoking them when necessary to maintain the integrity of your interactions with RapidStream’s APIs.