From Kaltura Player API (Kaltura Player - Fast, Flexible, Video Player Toolkit - api), the kWidget.settingsObject indicates that the Widget id is usually the partner id prefixed by underscore. As per our understanding, this should be a static value from one video to the next. However, we are finding that the Widget id is changing for each video and the format is different (ex. 1_sgbk6vm8). We get a video not found when trying to using the Widget id with the partner id prefixed by underscore as specified in the documentation.
Is the Kaltura Player API documentation incorrect for the Widget id or is there a setting that controls this value?
As you’ve correctly noted, the
wid can be set to
'_' + PARTNER_ID (and often is, for example, in KMC’s embed code generator). However, Kaltura also has a
widget service (see https://developer.kaltura.com/console/service/widget?query=widget).
widget.add(), you can create a custom widget ID with specific attributes. That will enable you to view entries for which content entitlement is enabled without setting a KS in the embed code.
You can easily check what attributes were set for a given widget ID by calling
Hi @jess ,
Thank you for the additional information. For users uploading videos in the portal, is there a way to always have the videos use the wid set to ‘_’ + PARTNER_ID instead of getting new values for every video?
Hi @abirkholz_mcf ,
A widget is created when generating a KMS embed code to enable the viewing/playback of media assets for which content entitlement is enabled. You can read about the content entitlement mechanism in the below documents: Content Categories Management - Kaltura VPaaS API Documentation
Content Entitlements and Privacy Enforcement - Kaltura VPaaS API Documentation
'_' + PARTNER_ID will not allow the viewing of media assets for which content entitlement is enabled unless a KS is set in the embed code.
If you want to bypass the content entitlement mechanism for a given media, you can associate it with a category for which no content entitlement is enabled (in addition to its other category/channel associations; one “open” category is enough). However, you can only do that via KMC or the API, it cannot be done from KMS.