Earlier today we announced the launch of our new DBX Platform, a unified suite of APIs and tools for developers. Since launching our first API in 2008, Dropbox has enabled over 500,000 developers to build connections to leading applications and tools. With your success, the platform has reached a scale of more than 2 billion API calls per day—and we’re just getting started.
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.
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 March 24, 2016] The official date of retirement for the Datastore API is April 29th, 2016.
Last week, we announced a preview of the new Dropbox API v2, aimed at simplifying the experience of developing with Dropbox. As part of this effort to simplify our platform, we’ve decided to deprecate the Sync and Datastore APIs over the next 12 months.
If you’re one of the majority of developers using the Core API, your app will be unaffected. For those using the Sync or Datastore API,
[EDIT June 3, 2015] This post has been updated to reflect the latest API v2 syntax.
We’ve been working on a new version of the Dropbox API for a while and it’s time to show you what we have so far. To start, we’ve implemented a select set of endpoints that highlight the big structural changes underway, and we’d like to know what you think!
Overall, we’ve simplified our use of HTTP. For example, most endpoints always use HTTP POST, including those that return structured data. Requests take JSON in the body and responses return JSON in the body.