Video Uploading Through APIs

Video Uploading Through APIs

Looking for a faster method to upload videos? Need one that isn’t restricted to accessing the dashboard of a video streaming, enterprise video streaming or virtual events platform account?

IBM is introducing video uploading through APIs. This allows organizations to upload video files into IBM’s video platform programmatically, without requiring access to the account’s dashboard. This opens new opportunities for uploading files while also being a faster approach versus the traditional dashboard uploading.


There are several different ways to get video content onto your IBM Video Streaming or IBM Enterprise Video Streaming account. Outside of auto archiving, the process in which a live stream is converted into an on demand version after the broadcast, the most common methods for adding videos are using the dashboard based uploader and Aspera Connect for custom level plans. A drawback to this is that both methods require that someone logs into the account.

By introducing the ability of video uploading through APIs, organizations can now develop methods for their employees or other individuals to add content to their account without having direct access to the video platform. In addition, it can be built into previous portals or infrastructures, streamlining the process from the uploader’s point of view. This can also be seen as a more security rich method, as opposed to giving someone direct access to one of the video steaming accounts.

In addition to broadening how content can be uploaded, the API based approach is faster for uploading video content than the traditional dashboard method. Consequently, files can be added in less time and by a larger group of approved people using these APIs.

Using the APIs for video uploading

Instructions for using the APIs to develop alternative workflows for video uploading are found on our developer site. This includes discussing how to initialize the process and existing parameters.

Please note that, for reliability in file uploading, the video needs to be uploaded in 1MB parts for this process. This will be behind the scenes for the end user or uploader, although needs to be configured by the developer.

Additional API VOD features

There are a wealth of other APIs available for customizing and managing video on demand (VOD) content after it has been uploaded. These features, while not mandatory, offer additional functionality and include:

  • Set a video thumbnail
    Can be used to upload an image file for use as a thumbnail or selecting a frame from the video for the thumbnail. Note that this is not required and that the system will automatically select a frame inside the video if not manually designated.
  • Trimming a video
    Allows moments at the start or end of a video to be trimmed out. Once trimmed, these moments will not be visible to the end viewer. This process is non-destructive and can be reverted at any time.
  • Setting an expiration date
    VODs can be setup with a limited window of access. This is done by establishing an expiration date, after which the content is no longer available. Note that this actually deletes the video from the account and is not advised if the asset might be needed at a later date.
  • Managing video chapters
    Chapter points can be setup inside a video. These are clickable links, with a short description, that will direct viewers to specific moments in the video.

This touches the surface of a few features available, although there are others related to VOD content that can be controlled through APIs. Other examples include managing closed captions, downloading videos, copying videos on the account, and more.


The video uploading APIs have several notable advantages over the dashboard methods. This includes developing it into existing workflows, speeding up video uploading and potential introducing a more security focused approach for video uploading.

The APIs are available now, and accessible over our developer site.