Greg-DB Dropbox Community Moderator

Yes, you can use the /files/create_folder endpoint: https://www.dropbox.com/developers/documentation/http/documentation#files-create_folder

Yes, you can share a folder via the API using the /sharing/share_folder endpoint: https://www.dropbox.com/developers/documentation/http/documentation#sharing-share_folder You can then invite members to it using /sharing/add_folder_member:…

The API doesn't offer a way to programmatically create accounts, but I'll be sure to pass this along as a feature request. 

You can use the ListFolderAsync and ListFolderContinueAsync methods in the .NET SDK to list the items in a folder. You can then count the number of files in your app's code.

Hola Javier, Este error indica que su aplicación está llamando a la API que indica un tipo de acceso esperado de "lleno Dropbox", pero la aplicación de la API que está utilizando es en realidad registrado para el tipo de acceso "carpeta de aplicación". Si refieres a utilizar acceso completo Dropbox, por el código que está…

After you list the files in a folder, you can use the DownloadAsync method in the .NET SDK to download the specific files you want, as identified by their paths. That returns the file content directly, but if you do need a link, you can instead use the GetTemporaryLinkAsync method.

No, unfortunately, I don't have an update on this yet.

I don't have an update on this yet. I'll reply here once I do.

Thanks! We're looking into it.

Hi Cynthia, thanks for the report! Can you share a sample X-Dropbox-Request-Id response header value from the error response? Thanks in advance! 

Thanks for the report! We're looking into it. 

Hi Karthik, there's no need to post the same question multiple times. I'll follow up in your new thread.

What error are you getting? Be sure to check the response body, as it will contain detailed error information. Based on your description though, it sounds like the issue is that you're calling /files/get_metadata for the root folder, which isn't supported, per the documentation: "Note: Metadata for the root folder is…

We have a new release, v2.0.3, that should fix this issue in the SDK itself, so that you'd no longer need that extra ProGuard configuration as a workaround: https://github.com/dropbox/dropbox-sdk-java/releases/tag/v2.0.3

Based on our investigation, you should be able to work around this issue by adding the following rule to your ProGuard configuration: -keepclassmembers class com.dropbox.core.** { @com.fasterxml.jackson.annotation.JsonCreator *; } We'll be addressing this issue in general in a future update of the SDK itself.

That's very useful, thanks! We're looking into it.

Thanks Kevin, that's helpful. I can reproduce the error using your app. Can you share the relevant code snippet(s)? We'll need to reproduce this separately, and there may be something different between your implementation and mine.

Thanks for following up. So, it sounds like you're seeing it for 100% of your calls to client.files().download()? Are other methods also failing, or are they working properly? I still can't seem to reproduce this though, even with the additional conditions you mentioned. Are your users seeing this issue too, or is it only…

Thanks for the report! I can't seem to reproduce this issue. Can you let me know about when you started seeing it, and about what percent of calls fail like this, to the best of your knowledge? Does it only happen for certain file paths? Thanks in advance!

HI Maulik, it sounds like you could use the shared links modifications I mentioned in my last reply: https://www.dropbox.com/help/201 And if you're using API v1 to get the shared links in the first place, you can set short_url to false to avoid the short links: https://www.dropbox.com/developers-v1/core/docs#shares

The Dropbox API doesn't currently offer a way to generate permanent direct links like that, but I'll be sure to pass this along as a feature request. What exactly do you need it for? If you just need to download file content, the normal download endpoints are the best option: v1:…

No, there's no workaround, beyond having the app ask the admin for their ID/email.

Dropbox for Business API apps are linked to Dropbox for Business teams, and not individual users/admins on teams. This can only be done by an admin, but the API doesn't currently return information about which admin specifically authorized it. I'm sending this along as a feature request though.

If you want to get a direct link to the file, you can use /media: https://www.dropbox.com/developers-v1/core/docs#media Also, please note that you're using API v1, which is deprecated. You should migrate to API v2 when possible. The equivalent endpoint on API v2 is /files/get_temporary_link:…

Shared links (modified for direct access) also give the same Content-Disposition unfortunately.

Hi Seth, unfortunately there isn't another way to get a different kind of link that would work for that, or a way to control the Content-Disposition on these links, so I'm afraid I don't have a good solution for you. I'll send this along as a feature request though.

Yes, users can export their datastores data from here: https://www.dropbox.com/account/security Apps with datastores data will have a "Download datastores" link. Users can use that to download a csv file containing the datastores for that app in their account. Hope this helps!

I see, thanks for clarifying. The /sharing/list_folders endpoint isn't supposed to list "SUB FOLDER" in that case, as that is just a normal folder inside a shared folder, and not a shared folder itself. You can use /files/list_folder[/continue] to list the contents of "FOLDER".

Hi Ashley, the /sharing/list_folders[/continue] endpoints should list all of the shared folders the specified user has access to. In your example, is "FOLDER" missing, or is it only "SUB FOLDER" that you're expecting and not seeing? The endpoint wouldn't list the subfolders (e.g., "SUB FOLDER") or other contents of those…

It sounds like the question here may be similar to your other thread. If you upload a (normal, not shared) new file inside a team folder, it doesn't have an owner exactly. That is, it won't be individually listed in /sharing/list_folders. It's just an item inside the team folder that any other editor can modify. You can…