Over the years, several different APIs and methods for interacting with Vimeo have come and gone.
In this article:
The Simple API was a basic way for users to get public metadata about their albums, channels, groups, users, videos. The URL structure for the Simple API looked like this:
This API is no longer maintained or supported. We recommend developers utilize our oEmbed implementation to get that same metadata for embeddable videos.
The Advanced API was a way for developers to read, write, and interact with metadata on Vimeo with authentication. The URL structure for the Advanced API looked like this:
This API has been fully deprecated and is no longer supported; requests to this API will fail. We recommend developers utilize our current API to interact with Vimeo resources.
On old vimeo.com pages, RSS feeds were provided to let users get updates about videos and feed activity. Some developers may have used these RSS feeds to bring Vimeo data onto their own sites or services. These feeds have been discontinued due to low usage.
RSS feeds should not be confused with MRSS feeds. Vimeo Pro, Business, Premium, and Enterprise users can generate MRSS feeds intended for use with custom TV apps. Learn more about this feature here.
Resumable PUT “streaming” upload method
The Resumable PUT “streaming” upload method was available up until the release of API 3.4 in early 2018. This method has been replaced by the open-source “tus” upload approach documented on the Developer Site.
We plan on permanently deprecating the “streaming” upload method with a future API update. No engineering resources are currently dedicated to maintaining the “streaming” upload method. To avoid service disruption, we recommend developers migrate to the “tus” upload approach as soon as possible.
Our in-house Creator Labs team released several libraries for integrating Vimeo with cutting-edge and experimental video technologies. The Unity SDK, A-frame/WebVR, and Max/MSP/Jittr libraries are not supported by our developer support team and any issues with those libraries should be ticketed in the respective repo on GitHub.