Greg-DB Dropbox Community Moderator

This output doesn't show the actual request/response for the API call. Are you able to retrieve the actual request and response showing the issue? I'm not aware of a bug on the Dropbox servers that should be causing this. This sounds like this earlier report we received, but we weren't able to identify or reproduce the…

@"DarioO" If you only needed to list the contents of a folder by using a shared link to that folder, you could use /2/files/list_folder and /2/files/list_folder/continue with app authentication. That would involve sending an app key and secret on both calls, and the shared link in the "shared_link" parameter on the…

@"Esikhoob" Здравко is correct; it looks like you're uploading the video as form data, but you need to send the original raw video data, not modified with any formatting or additional encoding. I confirmed that the file you shared starts with "------WebKitFormBoundaryaCK6EdHRBgQMkUuo..Content-Disposition: form-data;".…

1. I'll check with the team on this to see if we can get some better clarity on this. 2. The /2/files/list_folder/longpoll functionality should trigger shortly after any changes in the relevant account's filesystem, based on the account connected to the cursor that was used. So in this case, that means that should fire…

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

The Dropbox API doesn't offer options for controlling the formatting/markup of that message. I notice the same thing happens when performing the share operation from the Dropbox web site though, so I'm moving your thread to the "Create, upload, and share" section to see if anyone there can help with this sharing feature…

If that path values are not set, that indicates that the item is not mounted under the account/root for that call. For example, you may be using an access token for an account that doesn't contain that linked item. To download a file from a shared link for a folder containing that file, you should use the…

@"jbcodes" I can't offer a guarantee, but it looks like it may be resolved as soon as today or tomorrow.

@"jbcodes" The team is working on a fix for this. I'll follow up here once it's released.

Thanks for the report! I'll check on this with the team.

I can only really offer help with the API itself, so for questions about the GUI, I suggest posting in a section like "Create, upload, and share".

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 you are using, * the steps to reproduce the issue, including relevant code snippet(s), but don't include any access or refresh token(s) *…

@"foranuj" The Dropbox API does have a general 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 as…

The sharing_info field, e.g., from /2/files/get_metadata, is optional and only returned, "if this file is contained in a shared folder". To turn a folder into a shared folder, so that you can then retrieve the shared folder ID like that and/or add members to it, you would use the /2/sharing/share_folder endpoint (or share…

@"squdan" Thanks for the information. In order to avoid that error from that method currently, you'd need to use an app registered for the "full Dropbox" access type instead of "app folder". Alternatively, you can download the entire contents of the shared link by programmatically accessing the shared links directly and…

@"squdan" I don't have an update on this case. Are you using an app with the "app folder" access type?

This error would occur because the user's account is currently banned from creating links. As Здравко noted, the Dropbox Python SDK is not currently updated to handle that particular error properly, so it raises a ValidationError instead, but I'll ask the team to fix that up.

This is still open with engineering, but I don't have any news on it yet. I'll reply here once I have an update to share.

@"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…