Greg-DB Dropbox Community Moderator

@"anoduck" In addition to Здравко's note, make sure you're supplying all of the necessary credentials. I see you're currently setting a refresh token and app key. That would be sufficient if that refresh token was retrieved using PKCE, in which case the app secret isn't used. If PKCE wasn't used to retrieve that app key…

@"Newbie8" I'll be happy to help with any issues you're having with the Dropbox API, but I'll need some more information. Please reply with: * the name and version number of the platform and SDK/library you are using, if any * the steps to reproduce the issue, including relevant code snippet(s), but don't include any…

Thanks for the post, and apologies for the confusion. These member folders each have their own shared_folder_id value as they are each a mounted namespace in the context of the team space (even though they're not technically a "shared folder"). Unfortunately there isn't a proper way to exclude or identify these member…

@"msmoe" Здравко is correct, Dropbox is no longer offering the option for creating new long-lived access tokens. Dropbox is switching to only issuing short-lived access tokens (and optional refresh tokens) instead of long-lived access tokens. You can find more information on this migration here. Apps can still get…

Please print out the full request and response. The response body should contain a more useful error message. Be sure to redact the access token though.

@"alirameez" I don't have any specific updates to share, but the team does continually make improvements if/when possible. If I try running the code that was included in the original post (though I lowered the 'sleep' value since it runs faster than that for me) now, it does run faster than described there originally. The…

@"Rolana" No, I don't have any news on this feature request.

@"Redcom6816" Здравко is correct; paths may not end with whitespace. The path in your example ends with whitespace so it was rejected with that error. You can find more information in the documentation here: https://www.dropbox.com/developers/documentation/http/documentation#path-formats . You'll need to make sure the…

The Dropbox API does not offer an integer version number. It offers the "rev" value, which can be used to detect changes, but is not a monotonically increasing integer. Check out the Detecting Changes Guide if you're interested in how to use the Dropbox API to monitor changes to files/folders. The Dropbox API also doesn't…

@"Fenoma" Здравко is correct. For more information, refer to the following resources: * https://dropbox.tech/developers/migrating-app-permissions-and-access-tokens * https://developers.dropbox.com/oauth-guide * https://www.dropbox.com/developers/documentation/http/documentation#authorization

You can find the documentation for the Dropbox API, including all of the request and response objects/fields, here: https://www.dropbox.com/developers/documentation/http/documentation For example, the "returns" section of the /2/users/get_current_account documentation shows all of the fields returned when requesting the…

It sounds like you're attempting to call /2/files/get_temporary_link on a file that has been individually shared with you, i.e., a "received" file, such as listed by /2/sharing/list_received_files. As this isn't mounted anywhere in your account, this 'path/not_found' error is expected, since the file is not available in…

No, the Dropbox API does not offer a way to retrieve shared links with that hostname. (Also, note that while it may technically work, using 'dl.dropbox.com' like that is not officially supported/documented. The officially supported modifications are documented here.) If your use case would be met with temporary links…

The Dropbox API does have a rate limiting system that applies to all account types, but we don't have specific rate numbers documented for that, and we cannot increase the limits for any particular app, user, or team. Apps should be written to handle these rate limit responses automatically. Also note that not all…

The sharing_add_folder_member method should either return a result, or raise an exception. I can't say based on this snippet what is happening with your code execution flow, so I recommend stepping through with a debugger to see where it is hanging or infinitely looping. Let me know if something is broken in the Dropbox…

Yes, the rate limiting system works per-user account, and that is one reason that having all of your end-users connect to a single Dropbox account is not recommended, as all of their traffic will be attributed to that one account. And yes, the API was designed with the intention that each user would each connect their own…

That "version" field in the documentation for any particular API endpoint is referring to the endpoint version number. (This is distinct from the API version number, which is "2" for the current version of the API itself.) The endpoint version is included at the end of the API route. When the endpoint is still on version…

@"Ivan_" The 127.0.0.1:52475 address seen in your screenshot is the address of a local server that should be used to programmatically receive the authorization code. Please refer to the examples as written to see how that is extracted: *…

@"trithanhnguyen" Yes, as Здравко indicated, it sounds like you're looking for the contents of your "team space", but note that by default, API calls operate in the "member folder" of the connected account, not the "team space", so you won't see the contents of your team space when making API calls by default. You can…

Dropbox does not have SCIM functionality publicly available. If you want to use Azure AD, please refer to this help center article, or for Google Cloud Identity refer to this help center article. If you're interested in developing your own integration, please refer to the team endpoints documentation here.

Thanks for the report. I've asked the team to fix that up. By the way, note that Dropbox does not officially support accessing 'dl.dropboxusercontent.com' directly like that. You should use 'www.dropbox.com' with the 'dl' or 'raw' parameter and follow redirects, as shown in this help center article.

It's not possible to get a refresh token without using the OAuth flow, but refresh tokens don't expire, so you only need to process the OAuth flow once per Dropbox account. You can find more information in the OAuth Guide and authorization documentation. There's also an example here that may be helpful.

If you're referring to using sharing_add_folder_member to add a member to a shared folder, there is a AddFolderMemberError.rate_limit that applies per 24 hours. Please wait 24 hours and try again. Otherwise, regarding any particular error you're seeing regarding files/folders on the Dropbox web site, please reach out to…

The sample in my post happens to use curl on the command line, but exactly what network client you use is up to you, depending on your use case, environment, etc. I can't offer help with the third party network clients themselves, but looking at that code, it seems you're missing the rest of the parameters for the…

I have a post here showing the basic flow of getting and using a refresh token to retrieve new short-lived access tokens on demand which may be helpful.

@"Ivan_" Здравко is correct, to receive the authorization code programmatically, you should use a redirect URI. You can find more information on how this process works in the OAuth Guide and authorization documentation. Also note that it is not possible to fully automate the OAuth process where the user chooses to…

@"RogueBotanist" As Здравко noted, the code you shared is written to move the folder itself. If you want to move a specific file, you need to set the from_path parameter to be the whole path, including file name, to the file that you want to move. Likewise, the to_path parameter needs to the be whole path, including file…

I see you're trying to call the /2/auth/token/from_oauth1 endpoint. If this is a new integration, you should not be using that endpoint. This endpoint is only meant for use if you have pre-existing OAuth 1 access tokens, and the oauth1_token and oauth1_token_secret parameters would refer to the old OAuth1 access token key…

I can't see for sure with the redaction in your screenshot, but it seems like you're attempting to access a folder in your "team space". By default, API calls, such as GetMetadataAsync, operate in the "member folder" of the connected account, not the "team space", so the contents of the team space won't be found by…

@"_shintaku_" You're not guaranteed to get everything back in one call to files_list_folder, so as Здравко indicated, make sure you implement files_list_folder_continue in addition to files_list_folder as documented. Also, here's an example of how you can check the type of a Metadata object.