Dow Jones needed to assess over 230 applications for GDPR compliance. Learn how they automated their internal process to collect, synthesize, search and access the data using the Dropbox APIs.
The Dropbox API allow you to manage and control content programmatically and extend Dropbox capabilities in new and creative ways. If you’ve ever wanted to explore the DBX Platform but didn’t know where to begin, we’ve just published a guide that will take you through the basic steps required to get up and running using the Dropbox API.
Through this step-by-step tutorial, you’ll learn all about building on the DBX Platform while creating a simple file organization app to help sort files within your Dropbox account.
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,
HTTP-based APIs often encode arguments as URL path and query parameters. For example, a call to the Dropbox API’s filename search endpoint might look like:
While URL encoding seems fine for simple examples, using JSON might have some advantages.
URL paths are complicated
In the example above, the first “+” is a literal plus sign because it’s in the URL. The second “+” represents a space because it’s in the URL query component. It’s easy to confuse the two since the encoding rules are mostly the same and sometimes the library functions are name something ambiguous like “urlencode”.