Versions Compared
| Version | Old Version 29 | New Version Current |
|---|---|---|
| Changes made by | Former user |
|
| Saved on |
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Introduction
User's access to services provided by the AminoTV API are handled by Licenses. In order to use a service, the user must first be issued a License to a Product granting access to the requested service.
Entities overview
Entity | Purpose |
|---|---|
| Product | A Product represents a collection of services to which a user may be granted access. Products are defined by the service provider. |
| License | A License grants access for one user to the services granted by one Product. A user may have several licenses. Licenses can be purchased, revoked and expired. |
There are different APIs used for issuing licenses to user and to manage licenses and products by BSS:
| Child pages (Children Display) |
|---|
Each API has same by meaning license and product resources but management API resources provide more data on represented object.
Licenses are immutable and won't change. In case client need needs to introduce changes to existing license licenses it must delete previous license licenses and create a new onenew ones.
DRM providers support
Irdeto integration
If Irdeto DRM and rights management integration is enabled for customer environment then all the calls which create/delete licenses will force Irdeto entitlements creation/deletion.
The management of Irdeto products is not supported within this API, which means that client is obligated to take care of creating/deleting needed products by themselves.
Postman collection
licenseV4CollectionLicenseV4.postman_collection.tar.gz - the archive contains collection and environment configured to use postman mock service.
You need to import collection and environment into postman, create another postman mock server to use and set it in environment.
Under the collection there are three folders:
- API Spec - which contains all request just as they appear on the swaggerhub.
- UseCase - under this folder there are typical use cases with examples and some tests, only to check response codes, this folder could be also used to run in postman collection runner.
- Helper - contains
Postman collection was created which can be used to explore API, use cases and has possibility to configure it to use with client environment or with mocked environment:
In the archive there is a collection itself and example mock environment. Both need to be imported into postman.
The collection consists of 3 folders:
API spec - just a plain listing of all available calls, those are not mocked.
UseCase - the folder contains typical API use cases, all of those are mocked and contain complete examples with requests and responses.
Helper - contains auth request which could be used to obtain Bearer token which then can be used with later requests to real server.
| Table of Contents |
|---|