Greg-DB Dropbox Community Moderator

Can you share the full URL of the page displaying the error, as well as the text of the error itself? Thanks in advance! 

The Dropbox API does have a rate limiting system, but we don't have any specific numbers documented. For reference though, the limits operate on a per-user basis. However, note that not all 429s and 503s indicate explicit rate limiting, but in any case that you get a 429 or 503 the best practice is to retry the request,…

@"RTS S." The issue that was originally reported here was fixed on Dropbox's side. This thread is very old now though, and things have changed since then. We now document that the /oauth2/authorize page should be processed in the user's system browser anyway. If you're not already doing that, please update your app to do…

That's correct, unfortunately DeletedMetadata doesn't include the file ID, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. For files, you can call /2/files/list_revisions with the path from the DeletedMetadata to get the history of the file at that path though,…

[Cross-linking for reference: https://stackoverflow.com/questions/55233124/how-to-upload-ipa-file-to-dropbox-using-fastlane-and-circleci ] I see that you're using a pre-built plugin made by a third party. We're happy to help with any issues you may be having with the Dropbox API itself, but since this looks like a…

If you believe these files are incorrectly restricted, please open a ticket with support so they can look into it. Thanks!

The Dropbox OAuth app authorization process supports two different "flows" or "grants": the "code" flow and the "token" flow. You can find more information on both of these in the Dropbox authorization documentation here: https://www.dropbox.com/developers/documentation/http/documentation#authorization From the snippet you…

It sounds like you're referring to the three device limit for Basic accounts documented here. That limit applies to the devices that can be connected to the Dropbox product itself, via official Dropbox applications, such as the official Dropbox desktop client or mobile applications. This limit does not apply to third party…

@"Psome" When downloading a file from the Dropbox API, it will just return whatever raw data was uploaded. Since in your case the file is displaying in the Dropbox web UI, it sounds like the issue you're seeing may be slightly different than the original issue in this thread. I'll follow up with you privately to see if we…

My (Java) app. needs to know how a Dropbox filesystem (or part of it) changes and also has changed while she's not running. The listFolderLongpoll API seems to be well suited for this purpose and my first tests are promissing. You can use the listFolder[*] methods to see what exists in the account, and what has changed.…

[Cross-linking for reference: https://github.com/dropbox/dropbox-sdk-java/issues/240 ]

I'm closing this as a duplicate of: https://www.dropboxforum.com/t5/API-Support-Feedback/Dropbox-with-React-Native/m-p/334449 

In order to use the Dropbox Chooser or Saver you need to pre-register the domains you'll use it on. You can do that by entering them under "Chooser/Saver domains" on your app's page on the App Console: https://www.dropbox.com/developers/apps If you don't do so, you'll get this error message when attempting to use the…

@"Daniel_Dosen" Thanks for the idea! I'll pass it along.

Thanks for the report! This looks like a bug on our side when using /2/files/list_folder/get_latest_cursor as opposed to starting from /2/files/list_folder. We'll look into it. I'll follow up here once I have any news on this issue.

1. No, the external ID is not local only. It is persisted on the Dropbox servers. 2. It's not possible to set the external ID manually via the Dropbox web site. You can use the API to set it programmatically. With the Java SDK, that's done via membersAdd or membersSetProfileBuilder.

It looks like you're printing out the file metadata from an API call that returns information about the file. To get the file's actual content, you should instead use /2/files/download: https://www.dropbox.com/developers/documentation/http/documentation#files-download 

The 'too_many_write_operations' error indicates "lock contention". That's not explicit rate limiting, but rather a result of how Dropbox works on the backend. This is a technical inability to make a modification in the account or shared folder at the time of the API call. This error indicates that there was simultaneous…

No, unfortunately there isn't a way to make the API return folders only, but I'll pass this along as a feature request. 

You should use the same headers, but the body is used for endpoint-specific parameters, which can vary by endpoint. The /2/files/list_folder and /2/files/list_folder/continue endpoints in particular do take different parameters. For /2/files/list_folder/continue, the body should only contain the expected "cursor" parameter…

Can you share the code and parameters you're using, and the output you're getting in that case? That way I can take a look and see what the issue may be. (Make sure you check the response body for the error. I suspect it's 'not_found' in this case, but it always good to check to be sure.) I've sent your feature requests…

Thanks for the detailed feedback! For listing revisions of files, /2/files/list_revisions does support namespace-relative paths directly. (I.e., supply the "path" parameter as "ns:12345678/relative/path/to/file".) Perhaps that would work better for your use case?

I don't have any news or a timeline for a fix to share for this unfortunately, nor do I have specific numbers to offer on what the maximum count/size is. Apologies I can't be of more help. I'll follow up here once I have any update for you.

Officially, the limit is 150 MB, the same as /2/files/upload itself. Some uploads larger than that will still work, as in your example, but we don't recommend it as they become less reliable. (The strict cut off, where the request will get rejected with a 413 error, is 300 MB.)

Dropbox file IDs are case-sensitive, so the samples you shared here are unique: id:T6nGbXWJXnAAAAAAAAAATQ id:T6nGbXWJXnAAAAAAAAAAtQ Note the "t" vs "T" in the second to last character. You can find more information on this in the Path Formats section in the documentation here.

Thanks for the feedback! I'm sharing it with the team.

The Dropbox API doesn't offer a direct way to get the total size of a folder's contents, but I'll pass this along as a feature request. If you need to know the total size of the contents of a folder, you'd need to list all of the contents using /2/files/list_folder[/continue] and then sum up the `size`s for all of the…

Thanks for clarifying. For this sort of use case, we would generally recommend having each user use their own account, and share the files via a shared folder. You could then use a full Dropbox app connected to each individual account to operate on the contents of the shared folder. That said, distributing access tokens…

The API was designed with the intention that each user would link their own Dropbox account, in order to interact with their own files. (And for apps using the "app folder" permission, each user would get their own distinct app folder.) To allow arbitrary users to do so, the app would implement the OAuth app authorization…

Yes, you can remove the team's access to a shared folder in the team space by calling SetAccessInheritanceAsync and setting the accessInheritance parameter to NoInherit. Likewise, you can do the same when creating a new shared folder using the same parameter and value on ShareFolderAsync. Either way, the team will no…