Frisbii Media is a subscription and checkout management platform that allows you to sell digital products, manage subscriptions, and handle user authentication (SSO) on your website or app.
Note
You may encounter the name plenigo throughout this documentation, in code examples, and in the API. This is due to an ongoing rebranding from plenigo to Frisbii Media. The platform, all APIs, and all integrations are identical — only the name is changing. Code references such as
plenigo.CheckoutorX-plenigo-tokenremain unchanged.
Key concepts
Company ID
Your unique identifier in the Frisbii Media system. You will find it in the Frisbii Media Merchant Backend under Settings → Developer. Every SDK and API call requires your Company ID.
API Access Token
A JWT (JSON Web Token) used to authenticate server-side API requests. You create it in the Merchant Backend. It must be sent as the X-plenigo-token header on every request to the Frisbii Media REST API.
See Authentication & API Tokens for details on how to create and sign this token.
Offers & Products
An Offer is what you sell to your customer (e.g. a subscription plan or a one-time purchase). A Product is the underlying content item. Offers are identified by a plenigoOfferId (e.g. O_6E487EBURRY35FOD0J).
Access Rights
After a purchase, Frisbii Media grants the customer an access right linked to a unique ID (accessRightUniqueId). Your backend can check whether a customer has access to a specific piece of content using this ID.
Customer ID
Frisbii Media assigns every customer a customerId. If you manage users in your own system (external user management), you can link your internal user ID via customerId (numeric) or externalSystemId (alphanumeric).
Two integration approaches
Approach | When to use |
|---|---|
Frisbii Media SSO | Frisbii Media handles login, registration, and user data. Recommended for new integrations. |
External User Management | You have your own login system. You pass your user's ID to Frisbii Media, which handles only checkout and access rights. |
Both approaches use the same checkout flow. The difference is in how the customer session is created and passed to the checkout.
Platform components
Component | What it does |
|---|---|
REST API ( | Server-side operations: create customers, prepare purchases, check access rights, manage subscriptions |
Customer API ( | Self-service operations authenticated by a customer session |
JavaScript SDK | Client-side checkout, SSO login/registration, and self-service portal embedded in an iframe |
Merchant Backend | Web UI to configure products, offers, checkout settings, API tokens, and more |