Announcing the first Vimeo Hackday! And a new API!
We’ve been hard at work building a brand new version of the Vimeo API (dubbed API 3.0) and we’d like to invite you to join us at Vimeo HQ to try it out!
We’ll be here May 4th from 11am to 7pm to help you build apps on the new API. The best creations will be featured on our blog and dev site.
Some of the new features your app can take advantage of are:
- Register for push notifications
- Create albums and groups
- Simplified video upload
- Easy access to a large collection of Creative Commons videos
As well as all the features of the Advanced API, including:
- Access a user’s Feed and Watch Later queue
- Interact with the Vimeo community
Come check it out!
When: May 4, 2013 from 11am to 7pm
Where: 555 W 18th St, New York, NY
New Developer Site!
Would you be totally flabbergasted if we told you that in addition to rebuilding Vimeo from the ground up, we’ve ALSO constructed a brand new site for developers who want to rock the Vimeo APIs? Well, start flabbering your gasts* — because it’s true.
We’re happy to announce our brand new developer site: http://developer.vimeo.com! Our API is all grown up and ready to move into its own 1 bed / 1.5 bath subdomain. Laundry is just around the corner.
Right now you’re probably staring incredulously at your screen while yelling, “Whoa!!! Tell me some of the amazing features of this new dev site so I can continue my quest to conquer all technology!!!” You got it. Check our techniques:
OAuth Tokens provided
We now generate an OAuth token for you when you create an app — this way you don’t have to set up a temporary page to authorize when you only want to interact with your account. Just copy and paste into your app. OAuth awesomeness!
Simplified documentation and navigation
Life is complicated enough, so we’ve tried to streamline our documentation wherever possible. Now, instead of having to look at multiple pages of docs, you’ll find what you need on one page, reducing the need to jump around. And just like your favorite library book about deep sea creatures that somehow survive in complete darkness, our documentation now has a table of contents. Just flip to the section you’re looking for!
Clearer upload requests
Upload requests now take the form of a more straightforward questionnaire. This enables us to get right down to bizness and reduce the back and forth involved in approving your app for uploading. Because time is money, people.
The Advanced API method list now has the playground baked right into it, so you can easily get involved in some hot call-and-response action.
A suave new look
Night time is the right time for accessing data via the API. Turn the lights down, pour yourself a beverage, and kick back with some stone cold support from us.
*We have no idea what this means, but it feels good to say it out loud.
More vimeo.videos.getSubscriptions changes
To be consistent with how it is handled on-site, we will be requiring read permissions for vimeo.videos.getSubscriptions starting on April 2. You will need to pass a user token to the call or you’ll receive an error.
Subscription method changes
To accomodate improvements to our subscriptions system, we have a few changes coming to subscriptions methods in the Advanced API.
The first change is that we will be dropping support for the
types parameter on vimeo.people.getSubscriptions. It will return all subscription types.
A new parameter is going to be introduced to vimeo.videos.getSubscriptions:
offset. The value passed should be the subscription_id from the last video on the previous page (a new field added to the response). Although not required, passing the
offset will ensure that there is no overlap or missing videos between pages. As part of these changes, we will also be removing the sort ability for vimeo.videos.getSubscriptions. Results will always be returned with the newest subscription video first.
These changes will take effect in one month, on January 16, 2012, but you should start passing
offset as soon as possible.
If you have any questions about these changes, please let us know in the API Forum.
More Method Deprecations
Effective today, the following Advanced API methods are deprecated:
These methods will no longer work after February 29, 2012. We apologize for any inconvenience this may cause.
Starting at 10:30 am EST (about an hour from now), all API methods that modify data will be unavailable. You will receive a 105: Service currently unavailable error. Everything should be back up and running by 11:30 am EST. All read methods will remain available during this time. We apologize for the inconvienience.
NYC BigApps 3.0 Competition
We’re happy to announce our participation in NYC BigApps 3.0. The competition, which offers $50,000 in cash and other prizes, is open to software developers who create the best new apps that utilize NYC Open Data to help NYC residents, visitors, and businesses.
If you’d like to participate, check out the rules for the competition.
If you’re curious about the other APIs participating in the competition, check out the list here.
Have fun and make something cool with our API! (and let us know if you do)
To make way for some internal improvements, we will be deprecating the following methods in the Advanced API:
and the following in the Simple API:
These methods will no longer work after September 30, 2011. There are no direct replacements for these methods, but we encourage you to use the subscription methods instead (vimeo.videos.getSubscriptions in the Advanced API or user/subscriptions in the Simple API).
We apologize for any inconvenience this may cause.
Streaming Upload API
We added support for streaming uploads a while ago, but now we’ve finally gotten around to documenting it! We also tried to clarify some things in our POST upload API that were giving people some trouble, so make sure to check that section out too.
Player API Updates
We’re happy to announce that we just released a whole bunch of updates for our Player APIs! Here’s a list of what changed:
New version of the API! We’ve added a bunch of new methods that you’ve been asking for, and added some extra information to things that were already there.
Totally rewritten API Documentation! Our player has changed a lot in the past few months, and unfortunately our documentation had not. This time, we wrote the documentation as we were retooling the API, so it should be completely accurate.
New version of Froogaloop! Froogaloop has been updated to be compatible with the new version of the API. We also changed the way it works (a lot like jQuery) to make it a lot easier to use. The example page has also been improved a lot (thanks to Joe!) and now includes every API method.
Be sure to check out the updated documentation and our new API Playground page. As always, let us know if you run into any trouble, have any ideas to improve the API further, or notice anything inaccurate in the documentation.