id - unique license resource identifier - auto generated value, this value is used when operating over license
type - resource type, must be 'License'
Attributes:
status - current license status, could be one of [PROCESSING, CHECK_INVALID, ORDER_ERROR, ACTIVE, EXPIRED, SUSPENDED, SUSPENDEDADMIN]:
ACTIVE - this is the only status which allows end-user to watch the content license was created for, it is default status for newly created o licenses
SUSPENDED - license was suspended by client through BSS or by AminoTV support via CMS
SUSPENDEDADMIN - license was suspended by AminoTV script
EXPIRED - license life time expired, managed by AminoTV scripts
ORDER_ERROR, CHECK_INVALID, PROCESSING - are internal statuses for matching orders with external systems (Hybris SAP)
start_date - timestamp when the license should become active
stop_date - timestamp when the license will expire
order_id - field used to store client generated order id, also used by internal scripts when purchacing/prolonging licenses with 3rd party services
renew_record.recurring - with setting this attribute client can specify should the license be auto renewable or not, if the attribute omitted then value from associated product used.
renew_record.expiry_date - expiration date of the licenses, if the renew_record.recurring attribute set to true then licenses renewal scripts will rely on this attribute to select licenses to process
purchase_record.price_currency_amount - price of the license in cents, if this is not provided the value from associated product will be used
purchase_record.price_currency_iso4217 - currency of the license price, if this is not provided the value from associated product will be used
purchase_record.purchase_timestamp - timestamp to set license purchase date, this could be useful when license created separately on client side and then added to system, if no value provided then current timestamp will be used
purchase_record.payment_method - the method license was payed with, as we do not support any billing system clients should manage payments processing by themselves and can just pass any convenient string here. Please note that for users license API payment method 'billing' will be used by default.
Product resource
Authorization
All BSS endpoints support API key authorization. The header named 'Authorization' with content "Apikey PUT_YOUR_KEY_HERE" must be passed with request.
BSS can get list of licenses with filters, all user licenses and single license. GetLicenses and GetLicenseById calls return an array of licenses with all relationships and also contain included section with all products associated to fetched licenses. GetLicenseById will return single license resource and associated product in included section.