In this sample, you will learn how to replace videos using the Dynamic Ingest API. Note that the API does not support operations on multiple videos - the code here simply loops over a data set to replace the videos one by one.
Overview
The Dynamic Ingest API call is exactly the same as it would be for ingesting new videos - the only difference is that you do not need to make a prior call to the CMS API to create the video object in the Video Cloud system and get an id for it. If the source video file at the specified URL is the same one originally ingested, you will simply get a new set of renditions. If the source file is new, you will be replacing the existing video. All videos will remain playable with existing renditions until retranscoding is complete.
Implementation notes
To get access tokens and make the API calls, it uses a proxy built by Brightcove Learning services.
Getting Credentials
Rate limiting
See Best Practices for information on rate limiting.
Replace videos app
Find all the code associated with this sample in this GitHub repository.See the Pen Dynamic Ingest API Sample: Replacing Videos (Legacy Ingest) by Brightcove Learning Services (@rcrooks1969) on CodePen.
Using the CodePen
Proxy code
In order to build your own version the sample app on this page, you must create and host your own proxy. (The proxies used by Brightcove Learning Services only accept requests from Brightcove domains.) A sample proxy, very similar to the one we use, but without the checks that block requests from non-Brightcove domains, can be found in this GitHub repository. You will also find basic instructions for using it there, and a more elaborate guide to building apps around the proxy in Using the REST APIs.