Greg-DB Dropbox Community Moderator

Thanks for the additional feedback!

That's correct, this API endpoint does not currently support apps with the app folder permission. I can't speak to why any particular feature was or wasn't implemented, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. 

Yes, that's correct. I'll pass this along as a feature request, but I can't promise if or when that might be implemented. 

Yes, Dropbox expects your webhook URI to respond relatively quickly, so you should not perform the actual work to be done before responding to the webhook HTTPS request. You should have your server send the work off on to another thread so it can then send the HTTPS response quickly. There's some information about this…

Thanks for the report! I just looked into this based on the request IDs, and this is due to "lock contention". You can find more information on that in the Data Ingress Guide. That guide refers to the standard API endpoints, but the same applies to temporary upload links too. We should certainly return a better error…

No, unfortunately, the Dropbox API doesn't offer the ability to do a wildcard search like this, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. While not ideal, as a workaround, you could list the full contents of the folder using /2/files/list_folder[/continue]…

Thanks for following up. I'm glad to hear you already found a solution. For reference, the official Dropbox API v2 JavaScript SDK doesn't offer native progress listeners for the standard download methods, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. 

I'm not sure I understand the first part of your latest comment. If something isn't working as expected with the Dropbox API with respect to that, please clarify. Anyway, yes, you can check if a given shared folder is mounted in the connected account. Check the SharedFolderMetadata, e.g., as returned…

Yes, you can technically use these methods to list the contents of an unmounted folder. To do so, you need to use the 'Dropbox-API-Path-Root' header with the "namespace_id" mode, set to the namespace ID of the folder, which you can get from the Sharing.ListFoldersAsync method. In the .NET SDK, that would look like this:…

The Sharing.ListFolders methods only let you list shared folders themselves. To list the contents of any arbitrary path, you need to instead use Files.ListFolder and Files.ListFolderContinue methods.

Thanks! That's helpful. We're looking into it. I'll follow up here once I have an update on this.

@"clarel" Thanks! I've asked the team to see if we can reduce that down further like that, though I can't make any promises.

@"clarel" We've eliminated the extra scrollbar when embedding a folder. Thanks again for the feedback!

Also, if you can share several 'X-Dropbox-Request-Id' response header values for these unexpected failures, that would be helpful. Thanks in advance! 

Thanks for the information! Yes, if you're not supplying the path parameter at all, it should list all of the shared links for that account. Getting a 'path/not_found' in that case is unexpected, so we'll look into it.

Please open a ticket here and we'll look into this to see how we can help. Thanks!

We've added functionality for removing the Embedder. You can find information on this under the "Removing the Embedder" section in the documentation: https://www.dropbox.com/developers/embedder 

We've added functionality for removing the Embedder. You can find information on this under the "Removing the Embedder" section in the documentation: https://www.dropbox.com/developers/embedder 

In order to get an access token for the end-user, you should implement the OAuth app authorization flow in your app. You can find information on this in the OAuth Guide and authorization documentation. Once you retrieve the access token for a user, you can store and re-use it for that user. We also recommend using one of…

The /2/sharing/list_shared_links endpoint is the right API endpoint for listing the shared links owned by a user, regardless of account type. The 'path/not_found' error indicates that there was nothing found at the path specified in the API call via the "path" parameter though. Double check that you're supplying a correct…

Got it, thanks! I'll send this along to the team. (I can't promise if/when it might be implemented though.) I can't speak to those third party automation tools though, as they're not made by Dropbox.

@"jaonphoto" Thanks for the feedback!

Thanks for the report! This looks like an issue on our side. We'll look into it and I'll follow up here once I have any update for you.

The /2/files/list_folder response doesn't include shared links for entries, nested or not. It does include the normal File/FolderMetadata for the entries though, so you can use that metadata in your app. To step back a bit though, what functionality are you trying to build? For example, if you then want to programamtically…

It sounds like you accidentally moved a "}" when copying in your shared link. The "path" parameter should be a top-level parameter, not part of the "shared_link" parameter object.

Thanks for following up. I see you did successfully rename the thread. Anyway, I understand that the shared link, e.g., as seen in the browser, is not the same for the subfolder as the main folder, but to call /2/files/list_folder for a subfolder, you don't actually need the shared link for the subfolder in particular. You…

To list the contents of a folder nested inside a folder, where you only have the shared link for that top folder, you can use /2/files/list_folder again with the original top-level shared link, but then specify the relative path of the nested folder (e.g. built from the returned 'name' fields), in the "path" parameter.…

Thanks for the additional information, and clarifying that you were referring to appending to an upload session. Anyway, regardless of whether you're using the single /2/files/upload endpoint, or the upload sessions endpoints, the Dropbox API should only be sending one response per request. (I also haven't heard any other…

@"racheldory" There isn't an option for sorting, but we'll consider it a feature request. For our reference, is this something you'd want to set in the Embedder options in code, or for the user to be able to set in the UI (or both)?

The 'has_more' field is a property of the response, not a parameter, so it won't be included in the API v2 Explorer "Request" section. You can find information on it in the documentation. It is always set (to either true or false), so in your second screenshot it looks like there's just an issue displaying that value in…