About Greg K.

Greg K. · ‎01-26-2018

The Dropbox API now offers the ability to download folders as zips. In the .NET SDK, that's available as: https://dropbox.github.io/dropbox-sdk-dotnet/html/M_Dropbox_Api_Files_Routes_FilesUserRoutes_DownloadZipAsync_1.htm

Greg K. · ‎01-26-2018

@OneLoginAdmin I'm not sure I understand what you mean when you say it "is pretending to use old app authentication?". The /2/auth/token/from_oauth1 endpoint is an API v2 endpoint that uses app authentication. That means it requires the app key and secret as Basic credentials, and takes the OAuth 1 access token key and secret as parameters in JSON in the request body. You don't need to enable anything to use that endpoint. You would just need the four valid distinct values: app key, app secret, OAuth 1 access token key, OAuth 1 access token secret. The invalid_oauth1_token_info error indicates that the OAuth 1 access token you're supplying is not valid. You only need to use this endpoint if you have old valid OAuth 1 access tokens (i.e., from API v1) that you need to migrate to OAuth 2, e.g., for use with API v2. Where did you get your OAuth 1 access token? Are you sure it's still valid? Please double check that you're sending the correct values. If everything is correct, please share the code that isn't working as expected so we can take a look.

Greg K. · ‎01-26-2018

My sample, using your structure but plugging in my own access token, is working for me in Chrome, Safari, and Firefox. What browser are you using? If you check using the developer tools, what's the actual HTTP response that you get?

Greg K. · ‎01-25-2018

That URL structure looks right for accessing file data via /2/files/download using a GET request. What exactly isn't working for you? What error or unexpected output are you getting?

Greg K. · ‎01-25-2018

Unfortunately, the Dropbox API doesn't offer a way to add a folder from a Dropbox shared link directly to an account via the API, without downloading and re-uploading it. We'll consider this a feature request for a way to do so.

Greg K. · ‎01-25-2018

It's only possible to nest shared folders in "team folders" in Business accounts. It's not otherwise possible to nest shared folders, regardless of account type. If you are operating on a Business account via the API, sharing folders works the same way, inside or outside of team folders. To share a folder you would use the /2/sharing/share_folder endpoint (or corresponding native methods in the SDKs): https://www.dropbox.com/developers/documentation/http/documentation#sharing-share_folder It's not possible to "unlock" nested shared folders for Pro accounts.

Greg K. · ‎01-25-2018

Do you have a question about using the Dropbox API?

Greg K. · ‎01-24-2018

That's correct, you should store the last cursor you received and occasionally call back to ListFolderContinue using it to retrieve entries for just the things that have changed since the last time you called. Cursors don't expire, but they can become invalid in some (relatively rare) scenarios, so make sure you handle ListFolderContinueError.Reset: https://dropbox.github.io/dropbox-sdk-dotnet/html/T_Dropbox_Api_Files_ListFolderContinueError_Reset.htm

Greg K. · ‎01-24-2018

As announced last year, API v1 has been retired. You can find more information in the blog post here: https://blogs.dropbox.com/developers/2016/06/api-v1-deprecated/ We notified developers by email, but it sounds like those emails unfortunately did not make it to you. Now that API v1 has been retired, further API calls to it will fail. You should migrate your app to API v2 instead: https://www.dropbox.com/developers For Objective-C, we recommend using the official Dropbox API v2 Objective-C SDK: https://github.com/dropbox/dropbox-sdk-obj-c The documentation there covers a few different supported installations methods. Now that API v1 is retired, you won't be able to use it to make any further API calls, so you won't be able to upload files via API v1, for example. Any files already in your Dropbox are unaffected though, and you can upload/download using API v2 instead.

Greg K. · ‎01-24-2018

The Dropbox API does have a rate limiting system, but we don't have any specific numbers documented, nor can we increase or remove the limits for any particular app, user, or team. Also note that not all 429s or 503s indicate explicit rate limiting, but in any case that you get a 429 or 503 the best practice is to retry the request, respecting the Retry-After header if given in the response, or using an exponential back-off, if not. For example, you can check the body of the response for a more specific error. If the error is 'too_many_write_operations', that's not explicit rate limiting, but rather "lock contention". There isn't a way to remove that limitation either, but there are ways to avoid it. You can find more information about that here: https://www.dropbox.com/developers/reference/data-ingress-guide

About Greg K.

Re: Is it possible to download folder/upload folde...

Re: Migration from v1 to v2 API - automatic token ...

Re: php read CSV file in dropbox

Re: php read CSV file in dropbox

Re: Save shared folder to my dropbox by API ?

Re: sharing folders inside folder via command line...

Re: Okay

Re: Files ListFolder and ListFolderContinue slow

Re: Drobox API V 1 error 400 depricated

Re: Too many write request on Javascript SDK Uploa...