Greg-DB Dropbox Community Moderator

@"w3Abhishek" Здравко is correct; you'll need to set token_access_type=offline on the authorization URL in order to receive a refresh token from /oauth2/token. Refer to the following resources for more information: * https://developers.dropbox.com/oauth-guide *…

Thanks for the feedback! The Dropbox web site offers the ability to disable comments on files. You can find information on that here. The Dropbox API unfortunately does not offer this ability, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though.

This should be fixed now. Please try again and let us know if you're still seeing any issues. Thanks!

Thanks for the report! We'll look into it, and I'll follow up here once I have any news on this.

I just tried the webhook functionality and it is populating the API v2 account IDs for me. I notice that the output you shared isn't in the original payload format that Dropbox sends in webhook notifications though. For instance, you have a key "ListFolder" whereas the Dropbox webhook payload contains "list_folder". So, it…

@"cloudlock" Also, make sure the original file/folder still exists at the time of the save call. Otherwise, if this still isn't working for you, please open an API ticket with the following details so we can check on this specifically for you: * the affected app ID * the affected account ID * a sample of the full request…

We don't currently have something on GitHub open for this. This forum thread serves as the reference for this request, and I'll follow up here if/when I have news on this.

I believe this is something we'd need to update the Dropbox Java SDK to support. I'll ask the team to do so, but I can't promise if/when that might be done.

Since the error occurs when the user's client is connected to your server, but doesn't occur when connecting directly to Dropbox, it sounds like the issue is related to their connection to your server. Unfortunately, we can't offer much help with that as we don't control your server and don't make Nginx or Apache…

Dropbox doesn't offer request logs like that, so unfortunately I can't provide a copy of the request that the client made. That kind of inspection would need to be done client-side.

@"pvr325i" Здравко is correct; based on that output, that error is coming from your http://localhost:3000 server, so you'd need to check on what it is doing on its /api/dropboxcallback page. For instance, check your server logs and debug the code it is running.

[Cross-linking for reference: https://stackoverflow.com/questions/78102817/is-there-a-way-to-update-dropbox-files-through-api ] @"kenzy" As Здравко said, you can control this behavior using the write mode. For instance, if you're using the Dropbox Java SDK like originally mentioned in this thread, check out UploadBuilder…

I see the first thread was about the Dropbox servers switching to using "Transfer-Encoding: chunked", which the client did not handle. We then switched the servers back to not using "Transfer-Encoding: chunked". I just checked and can confirm that the servers are still not using "Transfer-Encoding: chunked" so that doesn't…

The www.dropbox.com website does not allow CORS requests, so attempting to access that from browser JavaScript will fail like that. There's also some information and options on these links here. Alternatively, if you want to programmatically download content from a shared link in JavaScript, you can instead use the Dropbox…

That doesn't seem to be the raw request, and regardless it's not the request to the Dropbox servers directly, so unfortunately we can't use that to debug this. Whatever the issue is, we'll need to be able to reproduce the issue to confirm what is going wrong and how to fix it. I replicated the request you shared earlier,…

@"tenzin" While I can't speak for others on this forum, Dropbox itself does not offer app-building services or have listings or recommendations of developers for hire, but I'll pass this along as a request for an offering like that. I can't promise if or when that might be implemented though.

@"jaksonjohn" The /oauth2/token endpoint is an OAuth endpoint, not a web page, and so should be accessed on api.dropboxapi.com, not www.dropbox.com. While it's possible that it happened to work on that domain previously, it was never officially meant for that and was not documented as such, and so would not be officially…

@"Bk13" Здравко is correct; the correct endpoint is and has been "https://api.dropboxapi.com/oauth2/token" per the documentation. Apps should not access that endpoint on www.dropbox.com.

@"kamzata" I moved your message to its own thread here: https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Re-Since-31-01-22-all-the-download-files-become-corrupted/td-p/754307 Please follow up there with the details so we can look into the current issue for you.

@"vewert" That should be fixed in the new v10.0.3 release. Please give that a try and let us know if you see any issues. Thanks!

Unfortunately I don't believe there's a workaround for that scenario, 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 aware of any issues that should be causing problems like that. I'll be happy to help however I can, 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…

@"SosiOne" Здравко is correct; that codeVerifier state needs to be persisted through the flow. You can find examples here: * https://github.com/dropbox/dropbox-sdk-js/blob/main/examples/javascript/PKCE-backend/code_flow_example.js *…

@"sz3324" As Здравко said, the request appears correct. I tried replicating the request as shown here and it did not fail like that for me, so please check that that's exactly what you're actually sending.

Thanks for the report! The Dropbox Chooser doesn't support choosing team folders or member folders themselves like this. I'll raise this with the team though to see if we can improve the interface or error handling for this.

It sounds like you're referring to the the GitHub secret scanning functionality, which can revoke Dropbox API access tokens found publicly posted on GitHub, so you would need to re-authorize the app to get a new access token (and optionally refresh token). If you're still missing webhook notifications though, I suggest…

@"MooMoo_polar" Здравко is correct; when using 'shared_link', using 'recursive: true' is not supported; you'd need to use 'recursive: false' and handle recursion in your own code if/as needed. You can find the documentation for the files_list_folder method in the Python SDK here.

There are a few reasons you may not be seeing webhook notifications: 1) Have you "linked" or "connected" or "authorized" the app to your account, before making the file changes, and is the account still connected? Webhook notifications will only be sent for changes in accounts that are connected to the app. When you create…

Dropbox doesn't offer a way to retrieve request/error logs like that, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. A 400 error like that would indicate an issue with how the request was formatted, and in cases like that we recommend using client-side logging to…

Unfortunately I don't have a solution to offer here as there isn't a global setting for that and the Dropbox API doesn't offer a way to control this, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though.