Integration Overview
Cleeng is a subscriber management platform. If you are a certified Cleeng partner or Cleeng Enterprise client, this guide covers everything you need to integrate subscription management, payments, identity, and content entitlements into your platform.
If you aim to sell subscriptions on your website, go directly to our Launch Subscriptions page.
Cleeng Overview
See the overview of the Cleeng ecosystem below and click on an image to go straight to the selected documentation section.
Integration Options
MediaStore Hosted Customer Flows, MediaStore API, MediaStore Components and the Core (3.1) API are the different ways of integrating with Cleeng when it comes to apps and client backend or middleware.
Main ways to integrate:
- Front-end integration (Apps communicating directly to Cleeng):
- Approach 1: Hosted Customer Flows-Based - the easiest, low-code and fast time-to-market solution (Recommended)
- Approach 2: Components-Based - using MediaStore Components
- Approach 3: API-Based - using MediaStore APIs
- Backend Integration (A server/middleware communicating to Cleeng)
Frontend Integration
Frontend integration - using either MediaStore Hosted Customer Flows, 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: Hosted Customer Flows-Based
Mediastoreās Hosted Widgets solution enables a low-code, fast setup with minimal development effort - this is the fastest and easiest way to get started with Cleeng.
Itās ideal for companies with limited developer resources or those who want to go live quickly as it allows you to embed a checkout on your website by copying and pasting a few lines of JavaScript code.
Configuration in the Cleeng Dashboard ensures rapid implementation. Automatic updates make maintenance hassle-free.
Approach 2: Components-Based
MediaStore Components - out-of-the box React JS components that can be integrated into your web app in order to provide a seamless experience for the end users.
š While MediaStore Components will continue to be supported for stability and security, we wonāt be adding any new features or expanding its functionality going forward.
It will remain fully operational and receive essential maintenance (such as bug fixes and security updates), but future development efforts will be focused on other areas.
Approach 3: 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 to have a side-by-side glance at the three approaches to frontend integration to help you make the best decision.
| MediaStore Hosted Customer Flows | MediaStore SDK Components | MediaStore API | |
|---|---|---|---|
| Integration Effort | 1 day | 1-2 weeks | 4-8 weeks |
| UX Customization | Branding, Themes (dashboard configuration) | CSS, Props, Themes (full UI control) | Complete freedom |
| Maintenance | Minimal ā Cleeng Managed | Update Components | Self-Managed |
| Update | Automatic | As Needed | Manual |
| Technical Expertise | Basic HTML | React.js Knowledge | Full Stack Team |
| Framework Support | Any | React.js based | Any |
| Ideal Use Case | Quick Launch | React Apps | Custom Requirements |
Backend Integration
For backend integration (Client server/middleware to Cleeng), you should use Core (3.1) APIs which are designed to integrate with Cleeng from the middleware or backend servers.
This integration method is for those who have an existing ecosystem and want to maintain the integration between their apps and middleware, while connecting the middleware to Cleeng.
Core APIs operate in the publisher context, using publisher token authentication, thus allowing additional flexibility, such as listing users, configuring webhooks or dunning settings.
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.
Build with LLMs
You can build AI-driven and agentic experiences on top of Cleeng. Instead of hand-coding every flow, you can use lowācode AI app builders and hosted experiences that already understand Cleengās subscription and identity model.
For more information, see the Build with LLMs article.
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 journey 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 necessary tasks are done before launching.
Updated 1 day ago