A little less than a year ago we announced June 28th, 2017 as the cutoff day for API v1. Developers have asked us for more time to finish updating their apps, so we have extended the API v1 cutoff date until September 28th, 2017.
Our goal is to provide developers with extra time to complete their migrations to API v2 and give users reasonable forewarning and time to respond to any dependencies on apps that have not yet acknowledged the API v1 deprecation.
We’re excited to announce that we’ve been working with Stack Overflow on the launch of their new Stack Overflow Documentation.
We’ve created a dropbox-api tag to organize answers to common questions about the Dropbox API and provide sample code snippets that you can easily use in your app. For example, here’s a topic for sharing a folder with a few snippets of sample code.
We’re also looking for your help! Stack Overflow Documentation allows the community to add their own topics and samples and collaborate on solutions via comments and chat.
Edit 06/23/2017: Deprecation timeline updated to match the one described in our recent blog post.
As of today, Dropbox API v1 is deprecated. This includes both the user endpoints (a.k.a. the Core API), and the team endpoints (a.k.a. the Business API). In order to provide our developers with the most up-to-date features and support a single, consistent platform, we’ll be turning off API v1 a year from now, on 6/28/2017.
API v2 is built thoughtfully with a consistent design and adds new endpoints and features. Additionally, we’ve open-sourced our SDK generator,
UPDATE JUNE 29, 2016 This post now has been updated to include new information about open issues.
Developers, it’s time to start migrating your apps to API v2. To help with this transition, today we’ve published a migration guide that will take you through all of the changes you’ll need to make to get your app running on API v2.
We are making breaking changes to the beta sharing endpoints, which will take effect as of February 24th, 2016:
- Reorganizing some error structures
- Changing the format of shared folder IDs
These changes help make error handling more intuitive and provide a better migration path for apps still using v1 endpoints.
Error Structure Changes
We’re improving and reorganizing the error structures for the beta sharing endpoints. For apps handling errors, changes will not be backwards compatible, but they will make error handling more intuitive in the future, especially as more features are added.
[UPDATE December 11, 2015] The following breaking changes are now available in the SDKs.
We’re making some improvements to the sharing features currently in beta. Specifically, we’re introducing paging support, and a new shared folder membership endpoint. We’ve also made some changes to how member errors are reported, as well as some of the fields included in SharedFolderMetadata. These changes will not be backwards compatible, but will allow for better scalability and ease of use.