|Video Cloud||All||Express I, Express II, Express III, Professional, Enterprise|
This topic gives you advance notice of forthcoming and past changes to the behavior of the Video Cloud service, Video Cloud Studio, or players that may require you to change the way you work with Video Cloud.
Brightcove has been hard at work delivering the next generation of online video technologies. Over the past 2 years, we introduced the Dynamic Ingest, CMS and Playback APIs to replace older integration methods with faster, better and more reliable technology.
With these newer APIs in place, we are beginning the process of deprecating the legacy Media API and FTP Batch XML systems. This document summarizes the timeline for this process and provides links to help you manage the transition. If you are currently using legacy Media API and/or FTP Batch XML, this notice should help you form a plan for migrating away from these legacy systems. If you are not using any of these APIs, no action is required.
On June 30, 2017, Brightcove will cease supporting the FTP Batch Provisioning System and the content ingest methods of the Media API. The Aspera upload method will cease to be supported at the same time. To add new content or to re-transcode existing titles in a Video Cloud account after June 30, 2017, all customers will need to use Dynamic Ingest. Introduced over 18 months ago, the Dynamic Ingest API supports all of the same formats and workflows as our legacy ingestion APIs and provides greater performance and scalability.
Also on June 30, 2017, we will be retiring the write methods exposed by the Media API (e.g., update_video) and all customers and partners will need to migrate their applications to the CMS API prior to June 30, 2017. The CMS API has been designed to improve the performance and flexibility of Video Cloud integrations and works with all of the latest features of the new Brightcove Player and Video Cloud Studio.
All of the CMS connectors managed by Brightcove have been updated to use Dynamic Ingest, and content ingested via this method can be published with the new Brightcove Player or the legacy Smart Player. This migration guide details how custom integrations can be migrated to the new APIs.
On December 31, 2017, the “read” methods of the Media API will be fully retired. Customers that have built client-facing applications (e.g., web pages or mobile apps) that depend on the Media API must migrate to the Playback API before December 31, 2017. The Playback API has been designed for high-volume read operations and provides the functionality and scalability required for large scale apps.
The iOS and Android SDKs have already been updated to use the Playback API. To support web site integration, in the coming quarters Brightcove plans to enhance the Playback API to support search queries, related videos and additional functionality commonly requested by customers.
To ensure that your sites and applications continue to operate smoothly, we strongly recommend you evaluate your current usage of these APIs and beginning planning migration to the newer APIs if necessary. During the transition periods described above, we will provide reminders about the timeline and additional information, tools and resources on moving to the new APIs. For more information, please consult the media management documentation. You can also contact your account manager for more details.
Deprecation of Media API read methods find_videos_by_user_id and find_videos_by_campaign_id. Effective January 31, 2012, Brightcove deprecated support for the Video Cloud Media API read methods find_videos_by_user_id and find_videos_by_campaign_id. These methods were used together with the old Consumer Generated Media module in Brightcove 2. For current best practices for managing user-generated content, see User Generated Content.
Deprecation of Media API read methods find_videos_by_text and find_videos_by_tag. Effective December 31, 2011, Brightcove deprecated support for the Video Cloud Media API read methods find_videos_by_tag and find_videos_by_text. We encourage you to use the search_videos method for video searches rather than using the find_video read methods. The search_videos method offers more flexible search and sorting options than the find_video methods, and is especially more flexible than the find_videos_by_text and find_videos_by_tags methods. For more information on the search_videos method, see Searching for Videos with the Media API.
Flash Player Support. Effective May 15, 2011, Brightcove no longer supports Flash Player 9 for using the Video Cloud Studio or Video Cloud players. Video Cloud Studio users should upgrade to Flash Player 10. Read more about why we're doing this and what it means to you.
Content type for Media API responses. The content type for responses returned by the Video Cloud Media API is application/json and not text/html. Using the application/json content type should provide superior security. The change in content type should not affect how any JSON returned in a Media API method is parsed.
Error returned by Media API search_videos method for invalid sort_by arguments. If you call the search_videos method in the Media API with an invalid sort_by argument, the error returned currently includes the text of the invalid argument. Calls that include illegal characters (such as <, >, &, \, %, or +) in the sort_by argument will return an error message with the illegal characters escaped.