BlendVision One provides API integration with your existing membership systems to restrict user access. 

This article details the features you can integrate with your membership management system, and the scenarios when you need to integrate the BlendVision API.

For the scenarios listed below, It’s required to integrate BlendVision API to enable their security features:

• Manage access tokens / concurrent device limits for private content: 
  Access tokens will be required for playing live events or VOD content when the visibility configuration is set as “Token”. 
  • If you plan to publish content using the embed iFrame player methods, you will need to integrate the BlendVision One API for generating access tokens.
  • The visibility feature does not apply to Player SDK solutions. If you plan to publish content using the Player SDK solution, you will need to develop the relevant functions within your system and integrate it with Player SDK.
• Display customer’s ID as watermark: 
  • If you want to enable the watermark function and set it as “User ID”, this option is only available for private content and requires API integration that requests tokens with your existing membership system for this type of watermark to function properly. 
  • The watermark feature does not apply to Player SDK solutions. If you plan to publish content using the Player SDK solution, you will need to develop the relevant functions within your system and integrate it with Player SDK.
• Poll/Chatroom in private live events:
  The BlendVision Chatroom system uses a different access token from BlendVision One. You will need to integrate APIs for generating tokens for chatroom/poll functions if you plan to publish your private content with the player SDK

For more information, please refer to our developer guide for the details on API integration.

If you need a customized integration plan, please get in touch with us via a support request.