Greg-DB Dropbox Community Moderator

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

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

1. 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 note that not…

Thanks for the notes! The team is working on a fix, and I'll follow up here once it's deployed.

Yes, as Здравко said, this is a known issue. The team is working on it and we'll follow up once we have a update on it.

Please check that the encoded app key/secret value you pass as "Basic" authorization in the "Authorization" header are properly encoded. Based on the error, it sounds like your value isn't properly encoded. Please refer to the "App Authentication" documentation for information on how to format this.

@"atonderski_zen" Thanks for the note! We'll follow up here as soon as we have some news on this.

@"amzp" Yes, even though the original author has marked a reply to this thread as a solution, we're still tracking this thread internally as a feature request.

@"amzp" This existing thread serves as the feature request for this. You don't need to create another one.

Thanks for the report! We'll look into it and follow up here once we have an update on this.

Thanks, that's helpful. Please try again but using an access token for an app with the "full Dropbox" access type instead of "app folder". There's currently a bug that can cause this error on this endpoint when calling with an access token for an app folder app. 

Thanks! Can you double check this sample is for a 'shared_link_access_denied' error though? This sample has a 401 status code, but errors like 'shared_link_access_denied' would be expected to have a 409 status code. A 401 indicates an authorization issue, like an invalid or expired access token, for example. In any case,…

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 access type (full Dropbox or app folder) of the app registration you're using * the name and version number of the Dropbox SDK/library you are using, if any * the steps to reproduce the…

@"Astrofrans" It's certainly possible to do so; you would just authorize the app for your own account only, and re-use the resulting refresh token for your account. The SDK works the same way regardless of how many accounts actually get connected. And while it's not the intended design pattern, as Здравко indicated, the…

First, by "MY ACCESS ID" and "MY_ID" I expect you mean your app key, and by "MY_PASSWORD" you mean your app secret, as this wouldn't work otherwise. Anyway, I just tried this out with an app with the app folder access type, and it did not create a duplicate app folder. Did you previously create, connect, and then delete an…

Correct, the Dropbox API is meant for use by end-users to each connect their own Dropbox accounts. You could technically connect to your own account only for everyone, but it's not recommended.

It's not possible to programmatically generate an access token without first using the OAuth app authorization flow, such as just from the app key and secret. The app authorization flow only needs to be done once per account though. For reference, Dropbox is no longer offering the option for creating new long-lived access…

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

@"marksmithhfx" We started rolling that out on or after April 13 of last year, so if this was more recently working for you, that may not be the cause.

@"marksmithhfx" As Здравко noted, that's not an error message/code from Dropbox itself, so I also suggest referring to the documentation for your client/platform. For reference, they mentioned TLS 1.2 as the Dropbox API only supports TLS 1.2 (and not TLS 1.1, or lower, for example). The error does mention SSL, so make sure…

The /2/files/download_zip endpoint is only meant for downloading folders from Dropbox, not files. (Dropbox zips the folder into a zip file on the fly for that.) To download a file (whether the file is a .zip file or not), you would use the /2/files/download endpoint instead. Also, it looks like your `path` value might be…

We've released a beta version of SwiftyDropbox with some significant updates, such as to remove the dependency on Alamofire. You can find more information here: https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Beta-version-of-major-SwiftyDropbox-update-available/td-p/695441

We've released a beta version of SwiftyDropbox with some significant updates, such as support for background sessions. You can find more information here: https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Beta-version-of-major-SwiftyDropbox-update-available/td-p/695441

While refresh tokens can be used repeatedly and don't expire automatically, they can become invalid at any time for a number of reasons (for example, if the user or app revokes it using the https://www.dropbox.com/account/connected_apps web page or the /2/auth/token/revoke API endpoint). If/when a refresh token is revoked,…

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

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

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

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

Thanks, yes, we're aware of and are investigating this issue.

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