This week I am writing about some small changes we have made to our API’s in the past few weeks. At Delve we believe in continuously improving our product -sometimes that means releasing bite-size features that nonetheless make our products more useful to our customers.

For instance, when a publisher uploads a video to our platform, the video is assigned a media ID which can then be used via the Content API to uniquely identify the video. Many of our customers, however, have large libraries of videos that already have unique ID’s assigned to those videos.

For these customers maintaining an association between the existing unique ID and the new unique ID the Delve platform assigns to each video is critical. That is why we just released an improvement to our API that lets a customer associate an existing unique ID to a video in our platform by using a special metadata property called “Reference ID” (See screenshot of the UI on this post). The “Reference ID” is a special custom property (unlike other custom video properties which we also support) because the value of this property can also be modified and viewed from our console UI.

In addition to the Reference ID property, publishers can now access the “Upload Date” and “Publish Date” properties via the Content API.

But wait, there is more! We have added more examples and sample code to our API documentation to make it easier for publishers to create rich websites. The Player API can be found here. The Content API and Analytics API documentation can be found here and here, respectively.