For example, OAuth 1.0 is no longer supported in API v2.The first thing that you need to do is go to the Dropbox’s developer site and create a new app.ĭropbox offers two APIs: the Dropbox API which is the API for the general public and the Business API for teams.

We also hope to make it easier for developers to build apps and to create SDKs.īy releasing a new version of the API, we also have the ability to part ways with old, deprecated endpoints and response fields. With these changes, we hope to make the Dropbox API easier to understand. This ensures that HTTP intermediaries, such as proxies or client libraries, will relay it along untouched. We chose 409 because, unlike many other error codes, it doesn't have any specific meaning in the HTTP spec. API v2 will always return a 409 status code with a stable and documented error identifier in the body. But if a request fails for some call-specific reason, v1 might have returned any of 403, 404, 406, 411, etc. For errors that are common to all API calls, we do the same thing as before: 400 for bad request, 401 for auth failure, 429 for rate limiting, etc. We've also simplified our use of HTTP status codes for errors. This allows browsers and HTTP client libraries to transparently cache that data for you.

file contents) support HTTP GET and ETag-based caching. For example, endpoints that return bulk binary data (e.g. We will continue to use other HTTP features in specific cases where they provide concrete benefits. Requests take JSON in the body and responses return JSON in the body. For example, most endpoints always use HTTP POST, including those that return structured data. Overall, we've simplified our use of HTTP.

Dropbox api status