We had to remove collections information from video responses for performance reasons. There is a new method available now to get a list of the collections that a video belongs to: vimeo.videos.getCollections.
We apologize for any inconvenience.
Activity in the Advanced API
In a few minutes, we’ll be pushing some backend changes to activity methods that will fix a number of bugs. Please let us know in the forums if you find any bugs.
Old Auth in v2
Just a reminder, we’ll be removing the old authentication mechanism from version 2 of the Advanced API later today (as announced).
We won’t be deleting any tokens though, so you can still use vimeo.oauth.convertAuthToken to convert your old tokens for awhile.
Today we announced the availability of our new Universal Player which allows just about any device to view a Vimeo video embedded on any blog. To achieve this, we used the iframe HTML element. While iframes are great for allowing you to host external content on a different site, they also come with a huge set of browser limitations in terms of security.
Upload API Enhancements
You can now replace a video using the Upload API!
Just pass the video_id of the video you’d like to replace when making your call to vimeo.videos.upload.getTicket and when you upload the file it will replace that video instead of creating a new one.
Old Authentication in API v2
We’re going to be removing the old Flickr-style authentication mechanism from version 2 of the Advanced API —at the end of this month, on August 31—. You will need to use OAuth to authenticate with version 2 from then on.
We’ve made it really simple to switch over: you can easily convert your auth tokens into OAuth tokens through the API without having to re-authenticate your users. (More information in this post)
Our latest PHP library is compatible with OAuth, so just drop it in and you should be good to go. There are plenty of other OAuth libraries out there for other languages too. There’s a great list on the official OAuth code page.
Updated: We’ve pushed back the date to September 15 to give everyone a little more time.
New Embed Code
We’re going to start testing a new embed code through the OEmbed API today. The new code is a good bit shorter than the old one, will validate properly, and should work in all browsers.
We’re adding a new parameter, xhtml, for you to use to specify if you want the code returned as HTML or XHTML; It will default to XHTML if you omit the parameter.
Let us know on the forums if you run into any trouble with it.
Starting next Wednesday (March 17) the oEmbed response will contain the largest thumbnail that fits within the size requested. Previously, the response would always include a 200x150px thumbnail.
See this post for the thumbnail sizes that are available.