Greg-DB Dropbox Community Moderator

I don't have an update on this yet. I'll follow here once I do. For reference though, if you don't need it, you can work around this by disabling the 'files.permanent_delete' scope for your app on the App Console.

@"dodnewtech50" 1) I believe that was a bug in an older version of the 'requests' library. Please update the version of 'requests' you have installed and try again. 2) No, these TLS changes do not require you to change your access token(s).

I see you’re experiencing an issue with a third party integration. Please reach out to the support organization for that integration for help. (If the developers of this integration are having any trouble with the Dropbox API itself, they can contact Dropbox developer support directly with the relevant technical details.)

You can use UploadSessionStartBatchAsync to start up to 1000 upload sessions. If you have at least 1000 upload sessions to start, you can do so in one call; you do not need to lower that. Calling UploadSessionStartBatchAsync once only counts as one call, regardless of what you set numSessions to. And you can call…

Dropbox APIアクセストークンの有効期限は、Dropboxアカウントのプラン/契約の影響を受けません。 Dropboxには、長寿命と短寿命の2種類のアクセストークンがあることに注意してください。 Dropboxは、有効期間の長いアクセストークンではなく、有効期間の短いアクセストークン（およびオプションの更新トークン）のみを発行するように切り替え中です。…

@"zangetsu" The file metadata shouldn't cause an issue like this. I do see that you're getting two different HTTP responses though, one with a 200 status code (for the successful file upload), and then one with a 400 status code (which can occur when the servers receive an invalid HTTP request). So, as Здравко indicated,…

@"Matias_FAC" No, I don't have an update on this request.

The 'too_many_requests' error indicates that your app is hitting the actual Dropbox rate limiting system. We don't have specific rate numbers documented, nor can we increase the rate limits for any particular, app, user, or team. Apps should be written to handle these rate limit responses automatically, respecting the…

The Dropbox API does have a rate limiting system, but we don't have specific rate numbers documented. Apps should be written to handle these rate limit responses automatically. Also note that not all responses with a 429 or 503 status code indicate explicit rate limiting, but in any case that you get a response with 429 or…

@"csingh-stripe" Dropbox does not currently have plans to implement this request. Please note that Dropbox is in the process of moving Paper documents into the Dropbox filesystem. Please refer to the Paper Migration Guide for more information.

@"ericchubb" I unfortunately don't have any update on this request. This functionality is still the same.

That's correct, since your access token is connected to the team itself, you'll need to specify a particular member to use a user API endpoint like /2/files/upload. You can find more information on that in the documentation under the "Member file access" section.

As long as the app allows you to re-connect the Dropbox account, you should still be able to use the integration for up to four hours at a time. Also, any data in your Dropbox account should still be there and accessible to you via Dropbox directly, e.g., www.dropbox.com, though that may or may not be useful depending on…

Dropbox is in the process of switching to only 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 though, in which case the app receives a "refresh…

A 'missing_scope' error indicates that while the app is permitted to use that scope, the particular access token you're using to make the API call does not have that scope granted. Also, be aware that just adding a scope to your app via the App Console does not retroactively grant that scope to existing access tokens or…

I'm sorry to hear about the issues you're having with this third party app, as well the trouble contacting the makers of the app. For reference, it sounds like the app is not handling short-lived access tokens properly. This is something that the third party app would need to be updated to handle. If the developers of this…

Thanks, that's helpful. It looks like your jistix-staging.com/oauth2/dropbox page is itself redirecting back to www.dropbox.com for some reason. It goes by fast in the log in your video, but here's the relevant portion: The authorize_submit page is the "Allow" action on the Dropbox app authorization page, which returns a…

Thanks for the report. This issue doesn't seem to reproduce for me though. Can you perhaps share a short screencast showing the issue? It may help to open the Network tab of the browser's developer tools first so we can see what requests are occurring.

@"LouisCorleone" Yes, that's correct. The Dropbox API still doesn't offer a way to retrieve this value directly.

@"Jistix_" You can work around this by disabling the 'files.permanent_delete' scope for your app on the App Console. (Of course, that's only suitable if you don't need that scope.)

Thanks for writing this up! I'm sending this along to the team to see if we can get this supported. I can't promise if or when that might be done though.

No, unfortunately I don't currently have a mechanism or documentation to offer for that; this is open with the team, but I don't have a timeline on if/when this would be done.

It's not possible to get a refresh token from an access token. A refresh token can only be retrieved by authorizing the app via the OAuth app authorization flow. (The "Generate" button on an app's page on the App Console does not offer the ability to get a refresh token; that only returns an access token.) To get a refresh…

Apologies for the confusion. The file sharing functionality offered by /2/sharing/add_file_member and /2/sharing/update_file_member does not support AccessLevel.editor for all file types. If you want to add editors to a file, you can instead put the file in a folder and share the folder via /2/sharing/share_folder,…

@"mayuri_thakare" Здравко is correct, this endpoint doesn't support "app folder" apps. You can find more information on the different permissions here. If you need to use this endpoint, you'll need a "full Dropbox" app instead. It's not possible to change that for an existing app, but you can register another app here.

@"Dmitri Bugryshov" Thanks for the note. This is open with engineering and I'll follow up here once I have an update on it.

@"xwbash" I see Здравко helpfully linked to some useful information. Let us know if you're still having any trouble.

Thanks for the report! I'm sharing this with the team to see if we can clean that up, but I can't make any promises myself. I'll follow up here with any updates on that.

Thanks for the report. This looks like a bug on our side with this configuration. We'll look into and I'll follow up with you here once I have an update on that for you.

@"dwissing" Здравко is correct, and offered helpful guidance, so please refer to that. Also, note that refresh tokens don't expire, so you can store and re-use them repeatedly.