Greg-DB Dropbox Community Moderator

Thanks for the report! We're looking into it. I'll follow up here once I have an update for you.

Thanks for the report! We're looking into it. I'll follow up here once I have an update for you.

As noted in the other threads you found, the /2/files/upload Dropbox API endpoint is a "content-upload" style endpoint, meaning it expects the file data in the HTTPS request body. The data should be sent just as a raw octet-stream (per the "Content-Type"), without any additional encoding. (Dropbox doesn't perform any…

@"Anonymous One" I see you also posted your own thread, so we'll follow up with you there.

@"Anonymous One" I see you also posted your own thread, so we'll follow up with you there.

@"Thang2000" Thanks for letting us know! I've updated the links in my previous post.

Yes, it's generally best to use /2/files/move_batch_v2 when you have multiple items to move/rename. Otherwise, there isn't a way to improve the speed of these operations on the API, but I'll pass this along as a request. I can't promise if or when that might be optimized though.

It is not possible to increase the permissions (e.g., add another scope) on an existing access token or refresh token. Adding a scope to your app via the App Console does not retroactively grant that scope to existing access tokens or refresh tokens. That being the case, to make any API calls that require that scope,…

The Dropbox .NET SDK is not built or tested for official support Maui or Xamarin, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though.

The Dropbox API does have a general rate limiting system that applies the same to all account types and API endpoints, 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…

@"jacky-radix" As Здравко said, webhook URIs are registered for apps, not accounts. Webhook notifications will only be sent for changes in accounts connected or "linked" to that app. If you haven't linked your account to your app, you won't receive webhook notifications for your account. I suggest reading the OAuth Guide…

@"Ivan_" For reference, does that flow in the original sample app work for you though? I highly suggest trying that out to make sure that works and see the flow processed fully before trying it out in your own code. In any case, when using a redirect URI, Dropbox will redirect the user's browser to the specified redirect…

@"iconify" These list_folder cursors do not expire by default, so they could last that long. However it is possible for them to become invalid at any time, due to some kinds of operations in the account, at which point /2/files/list_folder/continue would return a 'reset' error. That being the case, make sure your app is…

@"Babaraba Abdabi" As Здравко mentioned, you shouldn't assume that a link constructed like that will be necessarily correct always. We don't officially support building links like that; I recommend trying out the 'no_one' shared link option that I mentioned and that Здравко reiterated, as it sounds like it would be useful…

@"dragon v2" Здравко is correct; you should use the endpoints they linked to (or corresponding SDK methods) to list the contents of a folder. The File Access Guide may also be a useful reference.

@"rahulj1" You'll need to write and test your own code to suit your particular use case, but it might look something like this: import dropboxdbx = dropbox.DropboxTeam(ACCESS_TOKEN).as_user(TEAM_MEMBER_ID)root_namespace_id = dbx.users_get_current_account().root_info.root_namespace_iddbx =…

There are a number of different things that can cause that error. Did you check everything listed in my previous message? Have you tried running the example code without modification first?

This error indicates that the application's code has not been implemented to support long-term access properly. This is something the developer of the third party application will need to update the code to accommodate. This isn't something you can configure as the end-user of the app.

The Dropbox API doesn't offer a way to get/construct the URL of a file on the Dropbox web site (like with "/home") exactly, but you can call /2/sharing/create_shared_link_with_settings with the 'path' set to the the file/folder, and 'settings.audience' to 'no_one' to get a shared link that would refer to the folder on the…

@"Babaraba Abdabi" Thanks for the feedback!

There are a number of scenarios that can cause the refresh to fail like this, such as: * missing/incorrect/malformed refresh token * revoked refresh token (e.g., when the user unlinks the app via https://www.dropbox.com/account/connected_apps , etc.) * missing/incorrect/malformed app key * incorrect/malformed app secret *…

Yes, the Dropbox API and .NET SDK do support refresh tokens. That sample requests "offline" access to get a refresh token in this line, the refresh token is received here, and the refresh token is used to make a client here. The client will perform the refresh process using the supplied refresh token automatically.

@"terryz" I'm glad to hear you got this working! When starting from a /s/...?dl=1 link, there may be multiple redirects that need to be followed, which the client would handle do by issuing multiple requests. A 400 error response indicates that that particular request (that is, the one to which the response is sent) was…

A 400 like that indicates that there was something incorrect about the HTTP request issued by the client. (When following the redirects from the original link, there would be multiple requests made.) For example, as we found it seems the client is incorrectly sending the fragment ("#") on that particular link. Ultimately,…

@"terryz" Other clients/browsers support the ability to correctly handle redirects as well as withhold the "fragment" portion of the URL (the "#" part) when sending requests. These enable them to go from the original URL through to the final URL where the file data is returned. Based on what I've seen in this thread it…

@"rahulj1" Please review my previous message. In order to access the team space, you'll need to set the "Dropbox-API-Path-Root" header, which can be done in the Python SDK using the with_path_root method. In your latest code, you still don't seem to be using the "Dropbox-API-Path-Root" header or with_path_root method.…

Thanks for following up. I've also tried with the latest version of Google Chrome but the issue still doesn't reproduce for me. Are you perhaps using an old/invalid web session? Please try signing out and signing back in to Dropbox and then refresh the https://www.dropbox.com/developers/apps/create page and try again.…

Thanks for the report. I just tried this out myself and I'm not getting that error. If you're still seeing this issue, can you let me know which browser you're using and the version number of the browser?

@"terryz" Can you double check that you only removed the "#" and did not otherwise modify the link? I can't reproduce that 404 with curl. Also, note that these /cd/0/get/ links that result from the redirects can each only be used once, so you'd need to receive the link and remove the trailing "#" before you issue a request…

I see you're trying to access the contents of a folder in your "team space". By default, API calls operate in the "member folder" of the connected account, not the "team space". You can configure API calls to operate in the "team space" instead though. To do so, you'll need to set the "Dropbox-API-Path-Root" header. You…