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, 2016This 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.

[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!

What’s different?

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.

Please note: Sometimes we blog about upcoming products or features before they're released, but timing and exact functionality of these features may change from what's shared here. The decision to purchase our services should be made based on features that are currently available.