Greg-DB Dropbox Community Moderator

No, unfortunately there isn't a way to work around this or perform these calls for deleted team members, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. 

You can use the ID for a folder (or file) to retrieve the metadata for the item using /2/files/get_metadata, by passing in the 'id' string in the "path" parameter. Here's a simple example of that, first getting the metadata by path, and then by ID: curl -X POST https://api.dropboxapi.com/2/files/get_metadata \ --header…

Thanks! Yes, we're also looking into what we may be able to do about it on our side. I'll follow up here with any updates.

Thanks for the report! It looks like this was due to an availability issue in certain regions. That should be resolved now.

@"racheldory" Got it, thanks! I'll send that along.

Thanks for the report. I just tried this myself and I was able to reproduce this warning in Chrome with a temporary link to a zip file with some junk in it. A txt file worked fine for me though as well. I also accessed my two temporary links directly, and the only differences seem to be, aside from the file data itself: *…

The Dropbox API doesn't offer a way to list/download files based on a particular prefix like this. You could use /2/files/list_folder[/continue] to list files and folders, filter the result to the desired files, and then download them using /2/files/download though. Those are links to the documentation for the HTTPS…

We recommend just using the official SDKs whenever possible, as they'll do most of the work for you, but you can certainly use the HTTPS endpoints directly if you'd like. You can find information on this in the authorization documentation, as well as the new OAuth Guide. Most apps currently default to long-lived access…

The team is reporting this should be fixed now. Please let me know if you're still seeing this. Thanks!

Unfortunately, exactly how you manage threads is outside the scope of support I can offer, as it's not about using the Dropbox API itself. Please refer to the documentation for your platform/programming language for information on how to use threads in your environment.

There are a few types of sharing on Dropbox, and exactly what the best thing to do will depend on your particular use case, but I'm not sure I understand exactly what the requirements are here. Do you need to be able to share files to your users, or have them send files to you, or both? If you just need to be able to share…

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…