We will be making major upgrades to the way we deliver video very soon. Because of this upgrade there are some API and webhook changes that will be occurring once we switch everyone over to this new video delivery method on July 11, 2016. If you are using the API or webhooks to get direct URLs to your video assets, please make sure to read this guide carefully and implement any necessary changes. If you have any questions, please email us!
The URL format for video assets returned by the API and webhooks has changed. You may have already noticed this. If you’ve stored any of the URLs returned by the API or a webhook before May 25, 2016, you’ll need to replace them with the new format before July 11, 2016 when we will be porting over all videos to the new video delivery method. Once a video has been ported, the old format URLs will cease to function.
The new URL format serves two purposes. The first is that it serves as a proxy which means that we will be able to change the location of the files in the future without your having to make any updates in the future. Secondly, the proxy takes care of authorization based on whether or not you opted-in to api file access.
Old format for URLs:
New format for URLs:
If you have any URLs stored that are in the old format, you'll need to replace them before July 11th, 2016.
As of May 25, 2016, the API and webhooks return URLs in the new format so that you can start swapping out any old URLs with the new ones.
Starting on July 11, 2016, you’ll need to opt-in to access the video assets returned through the API. We’ve added this security measure so that those who do not access videos through the API, webhooks, or don’t use the API don’t have to worry about unauthorized access to their videos. If you try to access any video files returned through the API without opting-in to API file access, a 403 error will be returned. If you are using direct URLs, please make sure to enable API file access before July 11, 2016. Click here to enable access.
The API and webhook response for a video will change slightly. Since we will be generating multiple versions of a video instead of just the two we made in the past, we’ve altered the API responses to reflect that. As of July 11, 2016, the API and webhooks will no longer return the following video asset keys:
source_video_url. Instead we will be returning the following:
As of May 25, 2016 the API and webhooks now return both sets of keys to allow you to start migrating away from the old keys as soon as possible.
If you need a one-to-one mapping of keys,
source. This change will occur on July 11, 2016, so please be sure to update your integrations before then.