Brightcove provides static URLs to video manifest files for assets in your Video Cloud library. This gives you the flexibility to manage your content in your own CMS, and deliver it using a custom security schema.
This is important for customers who have existing architecture that does not allow a Playback API call before needing the manifest url(s). The player can also use this feature, reducing playback start time by eliminating one call.
Also see the Playback API v2 reference.
The following requirements are needed for static URLs:
- Brightcove Playback API v2
- Your assets are ingested for Dynamic Delivery
With static URLs, you are integrating with the Playback API without using the Brightcove Player. While the Brightcove Player automatically sends analytics data to Brightcove, you will use the Data Collection API to do this.
If you are not familiar with the Data Collection API, review the Overview: Data Collection API document.
For details about sending information to the Data Collector, see the Data Collection API Sample.
Today, every playback through VideoCloud requires 2 API calls to start video playback. With the use of static URLs, you can reduce the number of API calls to just one.
The following diagram shows the API calls for video playback WITHOUT static URLs.
With Brightcove's Playback API v2, static URLs are now available.
Here are the features associated with static URLs:
|Video-On-Demand (VOD)||Supported video formats via Dynamic Delivery only:
|VOD assets||Thumbnails and poster images|
|Authorization||JSON Web Token (JWT)|
|Delivery Rules||VOD only|
|Server-Side Ad Insertion (SSAI)||VOD and Live|
Brightcove’s CDN will continue to deliver the manifest and sub-manifests.
Customer's CDN will deliver only the video segments.
|Closed Captions||Only in-manifest captions are currently supported.|
|Playback Rights Service (EPA)||Contact your account manager for details.|
|Delivery Rules||VOD only|
Implementing Static URLs
Static URLs include the following:
- Account ID
- Video ID (or reference)
- Delivery Type (HLS, Dash)
- Configuration options (SSAI, DRM, CDN, etc.)
Static URLs are secured using a customer-generated and signed JSON Web Token (JWT). With this token, you can configure and enforce aspects of delivery. For details, see the Creating a JSON Web Token section.
The domain used for Static URLs is the Playback API v2 (PAPIv2) URL:
Static URL examples for each Delivery Type:
|HLS Master Manifest||
|Highest Bitrate MP4||
|Lowest Bitrate MP4||
- [1-1] HLS and DASH VMAPs can only be retrieved if you include the
ssaiclaim when you create the JWT - see the following section.
||JWT see below|
Creating a JSON Web Token
To create a token to use when communicating with Brightcove's Playback API, see the Creating a JSON Web Token (JWT) document. You will find the claims that can be used for static URL delivery there.
Using Content protection (DRM)
You can include the
pro claim, as defined above, to specify a protection type.
For license requests, the JWT does not need any payload, but it has to be signed using the same RSA key as the manifest request JWT.
Widevine license request
You can use the following endpoint to get the DRM license for Widevine:
FairPlay app cert
For FairPlay app certificates, the endpoint is:
For PlayReady, the endpoint for the licence request is:
The following notes apply to Static URL Delivery:
- In-Manifest captions are supported. Out-of-band sidecar captions will be supported in a future release.
- The customer's BYO CDN will deliver the video segments, while Brightcove's CDN will continue to deliver manifest and sub-manifests.
Brightcove supports using a JWT that does not expire. To do this, exclude the
expclaim when creating your token.