The application is built as a single page web app that can run without its own dedicated backend. This is useful for hosting it with a very simple, static host, like github pages. The server serves the static web content and the frontend calls the JW Player Delivery API directly. However, for additional functionality, the application can also connect to other backends to provide user accounts / authentication, subscription management, and checkout flows.
This API is a lightweight demo backend built to support the minimal backend functions, such as auth and content protection, that can't be done through the frontend alone. For more information, including how to deploy it, see the easy deployments document.
This API is written to be a conainerized Node application, so it should be possible to port it to another cloud or hosting platform without much trouble.
The available backend integrations serve 3 main roles, Accounts, Subscription, and Checkout. Below are the methods that any backend integration needs to support broken down by role:
- Account
- login
- register
- getPublisherConsents
- getCustomerConsents
- resetPassword
- changePassword
- updateCustomer
- updateCustomerConsents
- getCustomer
- refreshToken
- getLocales
- getCaptureStatus
- updateCaptureAnswers
- Subscription
- getSubscriptions
- updateSubscription
- getPaymentDetails
- getTransactions
- Checkout
- getOffer
- createOrder
- updateOrder
- getPaymentMethods
- paymentWithoutDetails
- paymentWithAdyen
- paymentWithPayPal
Cleeng (https://developers.cleeng.com/docs)
The OTT Web App was initially built around Cleeng, and Cleeng is an all-in-one platform that provides support for all of the 3 functional roles above. For configuration options see configuration.md