The get_temporary_upload_link API endpoint is now officially out of preview and available for production use. Developers can use this API call to get pre-signed upload URLs.
One of the most common actions a Dropbox integration will perform is to add new content.
The upload endpoint is used to push binary content to Dropbox. This is perfect for apps where the file is local to the machine connecting to Dropbox. However, for some types of client-server applications that integrate with Dropbox, this may be not optimal. For example, you may have a server-based application which manages all state and interaction with Dropbox and a mobile client that connects your server.
Dropbox is all about enabling teams to easily collaborate around content. There are many use cases for integrating directly with the Dropbox API, but there are also some scenarios where integrating with a workflow automation platform will allow you to ship a great solution faster than building them yourself. Whether you’re building out workflows for your company, customers, or yourself, Workato uses the Dropbox API to help you automate processes around content in Dropbox and other applications.
Workato can poll for Dropbox events or receive events using webhooks.
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.