Greg-DB Dropbox Community Moderator

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…

I'll be sure to follow up on this thread with any updates on this request.

Thanks for the feedback! I can't speak to the technical feasibility, so I can't say that it couldn't be implemented. I've sent this along as a feature request, but I can't promise this is something the team will be working on.

No, unfortunately there isn't a way of determining which file(s) were uploaded by which file request, but I'll pass this along as a feature request. I can't promise if/when something like that would be implemented though, so as a workaround you may want to change your setup to use a separate folder for each file request.

If you're a programmer, or are working with one, you can use the /2/files/save_url endpoint to programmatically save files from URLs to your account. (That's a link to the documentation for the HTTPS endpoints themselves, but we recommend using one of the official SDKs if possible. Those have corresponding native methods…

The links returned by getTemporaryLink unfortunately are not meant for displaying the file in the browser, per the documentation: this URL should not be used to display content directly in the browser The Dropbox API doesn't offer a good way to do that, but I'll pass this along as a feature request. I can't promise if/when…

Unfortunately, the links returned by get_temporary_upload_link do have a file size limit, as you found. Apologies this isn't better documented! I'll ask the team to clarify this. There isn't an alternative though, so that does mean that in this case, to upload large files, you'd need to either give the access token to the…

By default, the /2/files/get_thumbnail endpoint will return a 64x64 thumbnail of the requested image. If you want a different size, you can request it using the "size" parameter. You can specify that the same way you specify the "mode" and "format" parameters. You can find more information, such as the sizes that are…

@"lrduques" Apologies for the trouble. Please try that forum link again; it should work now.

Yes, if you want to continue using v2.1.1 for now, you'll need to update your code, at least to handle that BadResponseException. The upgrade from v2.1.1 to v3.* shouldn't be too significant though. The only breaking changes should be the two mentioned here: https://github.com/dropbox/dropbox-sdk-java/releases/tag/3.0.0 

Thanks for the report! We recently made an update to the /2/sharing/create_shared_link_with_settings endpoint (which is what createSharedLinkWithSettings calls). It wasn't a breaking change, but it looks like a bug in older versions of the Java SDK can cause the SDK to not properly handle it. Please update to the latest…

No, unfortunately the API doesn't offer a way to do this, but I'll pass this along as a feature request. 

@"hgkshin" That's correct, there hasn't been any change to this I'm afraid. I'll add your feedback to this feature request.

To clarify, were you calling /2/sharing/create_shared_link_with_settings with the "path" for that "Original" folder itself, or with a path for a file inside that folder? Note that the /2/sharing/list_shared_links works in the two different following ways: * "If no path is given, returns a list of all shared links for the…

This InvalidAccountType error indicates that the connected account (for the access token being used) doesn't have access to the feature you're trying to use via the API. If something isn't working as expected for you, please share the steps to reproduce the issue, and the relevant code snippets.

@"Ritesh2" Unfortunately, the file properties functionality is not support for apps with the app folder permission. I'll send this along as a feature request for support for that, but I can't promise if/when that would be implemented. If you need to use the file properties functionality, you'll need to register a new app…

I'm glad to hear you already sorted this out. To confirm, yes, when using an app with the app folder permission, the paths you use should be relative to the app folder itself. You can get these path values programmatically from other Metadata objects in the 'path_lower' field, e.g., as returned by /2/files/list_folder.

Unfortunately, the Dropbox Chooser is only built for standard browser environments, and isn't supported in environments like this, e.g., in a Firefox extension. That being the case, I'm afraid I can't offer any solution to these issues. I'll send this along as a request for support for this scenario, but I can't promise…

The Dropbox API operates by receiving API calls via HTTPS requests. So, by definition, the Dropbox servers do see the IP addresses of the clients making the HTTPS requests. For information on what kind of data Dropbox collects, please refer to our privacy policy: https://www.dropbox.com/terms#privacy By the way, from your…

Thanks for the feedback @"Tantara1" !

The Dropbox API doesn't offer the ability to programmatically upload to a file request, but I'll pass this along as a feature request. Instead, you might want to check out /2/files/get_temporary_upload_link instead, in case that works for your use case.

To access the account information, including the account ID, for the account for the access token you're using, you should use the /2/users/get_current_account endpoint instead of /2/users/get_account. That doesn't take any parameters, and instead just returns the account information based on the access token used for the…