Getting Started - Overview
Welcome to Cleeng Developer Portal!
Get ready to build your ideal OTT platform with a smooth checkout process that makes it super easy for your customers to make purchases. Plus, our self-service customer accounts let users manage their subscriptions and personal info on their own, ensuring an improved overall experience.
We invite you to explore all the amazing options Cleeng has to offer. Our solutions are designed to meet your needs, helping you create a strong and efficient platform in the bustling OTT market. Whether you’re looking for flexible monetization options or insightful analytics, we’ve got what you need to succeed and deliver the experience your audience will love.
Take a look at the overview of the Cleeng ecosystem below, jump to the sections that interest you, and explore all the fantastic things you can achieve with us!
Cleeng Overview
See the overview below and click on an image to go straight to the selected documentation section.
Integration Options
MediaStore API, MediaStore Components and the Core (3.1) API are the main ways of integrating with Cleeng when it comes to apps and broadcaster backend or middleware.
Two main ways to integrate:
- Direct integration (front end app to Cleeng):
- Approach 1: Components-Based - using MediaStore Components
- Approach 2: API-Based - using MediaStore APIs
- Backend Integration (Client server/middleware to Cleeng)
Direct Integration
Direct integration - using either MediaStore Components or MediaStore APIs (depending on the approach you select) - allows you to integrate apps with Cleeng directly, without middleware. This integration supports the end user context, so it will use JWT token for authentication and it will allow to carry out any activity in the context of the end user.
Approach 1: Components-Based
MediaStore Components - out-of-the box React JS components that can be integrated into a web app of a broadcaster in order to provide a seamless experience for the end users.
Approach 2: API-Based
MediaStore APIs - a set of APIs that allow you to integrate from the frontend app directly with Cleeng without the need to use any type of middleware or backend services.
See the overview of MediaStore API below and click on a tile to go straight to the selected documentation section.
Quick Comparison
See below and have a side-by-side glance at the two approaches to direct integration to help you make the best decision:
| Approach 1: Components-Based | Approach 2: API-Based |
|---|---|
| 1. Use the MediaStore SDK NPM Package 2. A pre-built solution that lets you embed ready-to-use components in your website 3. Much less building and maintenance work involved 4. Some styling and customization possible 5. Suitable for React.JS apps and Android TV (via web browser). Please note that in the case of Android TV there might be some limitations due to navigation via Remote Control Unit. | 1. Use MediaStore SDK API 2. API endpoints that you need to build your own flow and to have full control over it 3. More coding knowledge and development resources are required to implement and maintain 4. A lot of flexibility in customization 5. To be used with any front-end technology |
Backend Integration
For backend integration (Client server/middleware to Cleeng), you can leverage Core (3.1) APIs which are designed to integrate with Cleeng from the middleware or the backend servers of the broadcaster.
This integration method caters for the needs of broadcasters who already have their ecosystem and who want to use what they have and simplify the flows by integrating the frontend apps with their middleware and then integrating the middleware with Cleeng.
This integration supports the broadcaster context - these APIs use API key (broadcaster token) for authentication, therefore they provide a more extended functionality and more flexibility when it comes to configuration. For example, using these APIs, you can configure webhooks.
See the overview of Core (3.1) API below and click on a tile to go straight to the selected documentation section.
Before you begin, make sure you have completed the Quick Start steps.
Cleeng Sandbox
The Cleeng Sandbox is a testing environment that allows you to know the main functionalities of Cleeng's production environment. It is also an environment designed to test implementations and functions. To find out more, see here.
Go Live Checklist
Cleeng Go Live Checklist is the place to visit both at the beginning of your jouney and once you have completed your integration.
We strongly advise you to consult it when you are starting out to see what is in front of you, what you can expect, and to plan accordingly.
When you have completed integration with Cleeng and you’re almost there to start selling, visit the Go Live Checklist again to make sure all the necesssary tasks are done before launching.
Updated 3 months ago