Greg-DB Dropbox Community Moderator

To follow up here, the team confirmed that they found and resolved the issue with the excessive 429 responses with HTML bodies as of late Friday. Apologies for the inconvenience. 

Thanks for the report. I'm not aware of anything that should have caused that, so please open an API ticket and let us know the relevant app name, webhook URI, and date/time of the traffic so we can look into this specifically for you: https://www.dropbox.com/developers/contact

The 'id' for a file or folder, such as returned by sharingGetSharedLinkMetadata, is not the same thing as a 'shared_folder_id', and the two are not interchangeable. In the flow we discussed, you would get the shared folder ID from user 1's side, anywhere you can get the metadata for the folder, such as from…

[ Cross-linking for reference: https://stackoverflow.com/questions/61291263/how-to-upload-file-to-dropbox-with-axios ] What is in the response body for the 400 error response? It should contain a more specific and useful error message indicating what the issue is.

[ Cross-linking for reference: https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Java-desktop-DbxWebAuth-with-withRedirectUri-NPE/td-p/411576 ] This DbxWebAuth flow is meant for use with web apps, via whatever web framework you might be using. The request and response objects in this basic sample initially…

Yes, that is just an example of using the upload sessions methods themselves. It doesn't have a progress bar implemented, so you'd need to implement it in your code and hook up your own progress bar. For example, between each filesUploadSessionStart/filesUploadSessionAppendV2/filesUploadSessionFinish call, you could update…

I'm happy to help with any technical questions or issues you have regarding the Dropbox API, but I can't offer HIPAA policy or legal guidance. For information on HIPAA/BAA on Dropbox, please refer to this help article: https://help.dropbox.com/accounts-billing/security/hipaa-hitech-overview As for the technical aspects of…

That's correct, this flow is part of the Dropbox web site, not the API. From the app's perspective, it can also store the shared folder ID when retrieving the preview_url. The shared folder ID is unique for shared folders across Dropbox, and consistent across accounts. So, you would see the same shared folder ID for API…

Sure, this would look like this: * the app calls /2/sharing/get_folder_metadata and gets the 'preview_url' for the shared folder from user #1's account (here's an actual sample from a test account: https://www.dropbox.com/scl/fo/dh2dl2yrb4xk52n/AAAzPALQwplEJLHvONWVy1XTa?dl=0 ) * the app sends that URL to user #2 * user #2…

@"AlexSeniorDev" No, files can't be restored after being permanently deleted, such as via /2/files/permanently_delete. Note that /2/files/permanently_delete is only available to Dropbox Business API apps though.

Based on "getaddrinfo EAI_AGAIN" it looks like this is a DNS issue, so I recommend debugging the DNS setup being used by the affected server to see why it may not be able to look up the Dropbox API content server hostname. You may need to contact the administrator of your DNS server (or switch to a different one).

No problem, thanks for clarifying! There's nothing you need to do about that. I'll check with the team to see if there's something we can or should do about that though.

Thanks for the report. Just to clarify, is this preventing the Embedder functionality from working for you? That message should just be a warning, not an error. 

Unfortunately it's not possible to customize the file request like this via the API, or have the file request owned by the app instead of the account, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. The name shown in "[...] wants you to add files" comes from the…

We'll be happy to help with this, but we'll need some more information about where and how this is failing. For example, is it failing on the call to /oauth2/token, and what error response are you getting? Thanks in advance! 

We're happy to help with any questions or issues you might have about the Dropbox API itself, but we can't debug or write code for you, especially when you're using a client not made or supported by Dropbox (in this case, oHTTP). You'll need to refer to the Dropbox API documentation for information on what formats and…

An 'incorrect_offset' error from /2/files/upload_session/append_v2 indicates that the call failed because the app supplied an incorrect "cursor.offset" value in the parameters. The app and the server need to agree about where in the upload process they are in order to upload exactly the right data. I recommend adding some…

@"knoppys" For reference, if your solution involves exposing the app folder access token client-side, we still wouldn't recommend this. Even if you remove the files from the app folder as soon as possible, someone with the access token could read any files while they do exist, or even after they're deleted by restoring…

@"UlfFahlen" Thanks for the additional report. We're looking into it. Note that the development/production status of your app wouldn't affect this.

@"jeji" I'll follow up on this thread once I have an update on this.

In this code, you're still putting the access token on the URL, but additionally with the string "Authorization". You should instead be sending this as a header. Based on the rest of your code, for your client that would probably look something like this: oHTTP:setRequestHeader("Authorization", "Bearer" + ctoken) Likewise,…

[ Cross-linking for reference: https://stackoverflow.com/questions/61251822/unknown-api-function-files-upload ] I've posted an answer on your StackOverflow question. Hope this helps! 

Yes, you can use this filesCopyBatchV2 method to copy files from multiple different locations into one folder. When doing so though, each 'to_path' shouldn't all be exactly the same. The 'to_path's can all be inside the same folder, but they should include the different file names so they don't conflict with each other.

It looks like you don't have a continuation "\" on the second to last line, like there is on the other lines, so the last line may not actually be given to curl which would result in no data being upload. Try adding that "\" back.

The app key is considered public and does not need to be protected. The app secret should ideally be kept private though. For server-side apps, such as web apps, this is possible since the app secret can be kept on the server only. In client-side apps, it's not possible to secure secrets unfortunately. Instead, you can…

Thanks for the report. It looks like we may be using a generic HTML error page in some rate limiting cases. We'll look into it.

I just tried this out myself in a test account for reference, and I don't think I'm seeing the same behavior. For example: curl -X POST https://api.dropboxapi.com/2/files/get_metadata \ --header "Authorization: Bearer <ACCESS_TOKEN>" \ --header "Dropbox-API-Select-User: <MEMBER_ID>" \ --header "Content-Type:…

This 'failure/relocation_error/to/conflict/folder' error indicates that the operation failed because there is already a folder at the destination path you specified. Note that when specifying a destination path like this, you should specify the full path where you want to put the item, including both the path of the parent…

Have you made any changes to the Java SDK project? If so, can you let me know what? Also, for reference, if you don't need to make changes we recommend that you don't build from source. If you don't need to make changes it's much easier to use one of the pre-built releases, e.g., via Maven or Gradle as documented here.

Yes, this is fine. Dropbox shared links don't break when editing the linked files, and I'm not aware of any plans to introduce a change like that. One note though, in general WriteMode.update is more recommended than the overwrite mode, as it's safer. Using overwrite can lead to your app overwriting new changes that it…