Greg-DB Dropbox Community Moderator

Thanks for the feedback!

@"awb" This is still open with engineering, but I don't have an update yet. I'll follow up here once I do.

A 'no_permission' error from /2/files/copy_reference/save means: no_permissionVoid You don't have permission to save the given copy reference. Please make sure this app is same app which created the copy reference and the source user is still linked to the app. You mentioned you're using two different apps, so it sounds…

It looks like you're trying to operate on files inside the "team space". In order to access the team space, you do need to use the "Dropbox-API-Path-Root" header. It's not possible to access the contents of the team space without using the "Dropbox-API-Path-Root" header, but there are different ways to use the…

@"Ashley B.15" Thanks, that's helpful. The /2/files/list_folder endpoint should certainly be publicly available so we'll look into this and follow up here once we have an update on this.

A 'route_access_denied' error should indicate that the call failed because the API route the app is trying to use is not publicly available. If it appears you're receiving this error incorrectly though, please reply with the following so we can look into it: * the name and version number of the SDK/library you are using,…

As Здравко said, you can use any language to access the Dropbox API as long as it can make network requests. For reference, Dropbox offers an official SDK for JavaScript, but not PHP. Using an SDK can make integrating with the Dropbox API easier. Use of an SDK for accessing the Dropbox API is optional though.

Thanks for the feedback! For reference for anyone reading, if there are no parameters to send for an RPC endpoint like this, you can omit the request body as long as you also omit the "Content-Type" header (since there is no request body to describe). To illustrate this, here's some examples of working usage of the…

The /2/sharing/update_folder_member endpoint does support the Dropbox-API-Select-Admin header, but only in the "Team Admin" mode, meaning it can "access content of team folders and team spaces but not the team members' home namespaces". So, for example, if that namespace is for a shared folder in the account's home…

The Dropbox API does not currently offer an endpoint directly using the "contacts.read" scope. The "contacts.read" scope exists as a dependency of the "contacts.write" scope (used by /2/contacts/delete_manual_contacts and /2/contacts/delete_manual_contacts_batch). The Dropbox API does not currently offer an endpoint for…

@"mikechiu" If you're still having trouble with /2/sharing/update_folder_member, as Здравко said, please share the details of the /2/sharing/update_folder_member call so we can take a look.

The Dropbox API does not currently offer Dash functionality, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though.

Thanks for following up. I'm glad to hear you sorted this out. Yes, for reference, the length of Dropbox access tokens is not guaranteed and may change over time.

@"awb" First for reference, note that the post you linked to is old and now somewhat out of date. As Здравко noted, new Dropbox API access tokens do now expire, and access tokens and refresh tokens can also still be explicitly revoked. There are different errors for these cases: 'expired_access_token' indicates the token…

@"JohnStrudwick" The Dropbox API does have a general rate limiting system that applies to all endpoints. Also note though that if there are multiple changes at the same time in the same account or shared folder, you can run in to "lock contention" (which uses the 'too_many_write_operations' tag). That's not explicit rate…

@"qaaperture" The Dropbox API also does not currently support created times for folders, but I'll pass this along as a feature request as well.

We've updated this to support passing in "null".

@"Geniatech" As Здравко noted, that error message does not necessarily appear to related. In any case, we'll look into it. I'll follow up here once I have any news on this.

@"Bk13" If Dropbox is repeatedly unable to successfully deliver webhook notifications to your webhook URI server, it will stop attempting to do so. At that point, your webhook URI will be disabled, you will be notified of this by email, and no further webhook notifications will be sent until the webhook URI is re-enabled.…

@"qaaperture" Здравко is correct; the Dropbox API does not currently support modified times for folders, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though.

@"synology_support" I just wanted to follow up here to let you know we've recently received several samples from users regarding this thread. I believe we've established enough of a pattern here that we do not require any further samples, so there's no need to send in more samples. I'll let you know if the team requests…

Please note that the files_list_folder/files_list_folder_continue interface is paginated, so you're not guaranteed to get all results back in a single page. The number of pages that are used can change over time and across accounts, folders, etc. Be sure to check the ListFolderResult.has_more returned by files_list_folder.…

@"Vlopez1" Given the description of the issue, such as how it works for you locally and only fails sometimes when using the remote device, it does sound like a transient network issue. While it wouldn't fix any network issues, you can configure the timeout for the Dropbox client using the "timeout" parameter on the Dropbox…

@"SJ_Code" It looks like your messages got caught in the spam filter for some reason. I just released them. Unfortunately I don't have a timeline to share for updates to the .NET SDK.

A server update caused unencoded header values to be rejected. We’ve updated the server to accept these requests again so this should be working now. However, the .NET SDK should have automatically handled this for you anyway, so we would still want to check on that. If possible, please share the answers to the questions…

@"awb" This was due to an incompatibility between the format of certain responses returned by the API and how the SDK was parsing them. The team updated the server to return responses that the SDK would parse successfully. There may be other cases of this though, so if you're seeing this currently, please share several…

Dropbox is no longer offering the option for creating new long-lived access tokens. Dropbox is now 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 long-term access by requesting "offline" access…

Thanks for sharing this. I tried out this code though, and it worked successfully for me. Can you confirm if this was the exact code that produced the error you saw? For instance, did you change any of the parameter values after you reproduced the issue before you posted this? If so, please share the actual parameter…

@"Nico-Uretek" I don't actually see any encoding being done on your header values in your code. Please make sure you have the encoding implemented as covered here.

@"Nico-Uretek" If you're still seeing an issue when applying the encoding as documented, please share the specific steps, code, and parameter value(s) needed to reproduce the issue you're seeing so we can look into it. Be sure to redact any access/refresh tokens though. Thanks!