API v2 developer site (preview!)

In April we announced API v2, a new version of our Dropbox API. Over the past few weeks, we also released preview versions of SDKs for Swift, Python, and .NET that work with API v2. And now we’ve put this all together in a new developer site, specifically for API v2.

Check it out: Dropbox API v2 preview developer site

The content is mostly the same as our previous blog posts, but now it’s in a single easy-to-find location.

Read more

Introducing a preview of the new Dropbox.NET SDK for API v2

[Update: API v2 and the Dropbox.NET SDK are no longer in preview and are ready for use in production.]

Today we’re announcing the Dropbox.NET SDK, a new SDK that you can use to try out our new API v2 preview. We’ve built this SDK to support the Microsoft development community and we’d love to get your thoughts and feedback.

The Dropbox.NET SDK is a Portable Class Library that works with multiple platforms including Windows, Windows Phone, and Mono.

Please keep in mind that both the SDK and API v2 are in preview mode so please don’t use them for your production apps just yet.

Read more

Now available in preview: Python SDK for API v2

We’ve been hard at work on API v2, and today we’re releasing a second preview SDK: the Dropbox Python SDK!

It’s no secret that we love Python here at Dropbox, so we hope you’ll try out the SDK and send us your thoughts. This blog post will show you how to install the Python SDK and help you get started making calls using the Dropbox API v2.

If you’re familiar with API v1, you’ll notice a few differences in this new SDK. For more context on v2, including an overview of how we’re updating the Core API,

Read more

A preview of the new Dropbox API v2

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

Read more