Greg-DB Dropbox Community Moderator

If you've reached "Successfully set up client!" in that sample, you've already successfully processed the app authorization flow and retrieved a refresh token. The refresh token is in 'oauth_result.refresh_token' in that sample, e.g., as used in line 25. For your actual app, you can store and re-use that.

It looks like you're running your python3.10.exe directly, and the window is closing automatically when the program completes (such as from the exit call, as you mentioned). I can't really offer support for your development environment itself as that's not made by Dropbox, but there are other ways to set this up so that…

Thanks! I'll let you know once I have any news on this.

Thanks for letting us know. I'll bring this up with the team. Can you also let me know if you're seeing this on all such calls, or only a portion? If it's not all calls, can you let me know roughly what percent of these calls fail like this for you?

@"phunction" You can find the default parameter values for GetAuthorizeUri in the documentation here. And that's correct, you can re-use refresh tokens; refresh tokens don't expire by themselves (though they can be revoked by the app or user on demand).

Apologies for the trouble with the spam filter. I just unflagged your posts. Anyway, I saw your new post and followed up there.

Can you elaborate on what you mean when you say "python just shuts down"? Is there any error/output? After line 19, you should either get an error printed via line 22, or execution should continue and perform the users_get_current_account call (though this minimal example doesn't actually do anything with the result) and…

1. Yes, using a refresh token is the right way to maintain long-term access without repeated manual interaction. 2. You can find an example of using the Python SDK to process the app authorization flow to get a refresh token here. Once you have the refresh token, you can store and re-use it to make the Dropbox client…

@"phunction" As Здравко indicated, setting tokenAccessType: TokenAccessType.Offline on GetAuthorizeUri is the right way to request offline access in order to get a refresh token, as shown in the example they linked to. You can find the full options for GetAuthorizeUri in the documentation. Also, please note that…

Thanks for following up. I'm not sure I understand your use case though. Can you elaborate? Why do you need to be able to retrieve the current short-lived access token? The recommendation is to just create the client with the credentials you have and let the client perform the refresh automatically, whenever needed (even…

Thanks for following up. I see you're using the Dropbox .NET SDK. As long as you supply the necessary credentials when creating the DropboxClient object, the SDK should handle the refresh process for you automatically, without you getting the expired access token error yourself or needing to call CheckAndRefreshAccessToken…

@"didouchk" In addition to what Здравко said, note that there is an Android-specific example here. Make sure you're implementing the authorization flow as shown. And if something doesn't seem to be working as expected, please reply with: * the version numbers of the Android platform and Dropbox SDK you are using * the…

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…

@"spotloader" This feature request was filed with the team, but I don't see any plans to implement it currently.

You can register an individual account for free here: https://www.dropbox.com/register Individual accounts like that have UserRootInfo.

@"Reshma " As Здравко indicated, you cannot use a refresh token as an access token. Refresh tokens and access tokens serve different purposes and are not interchangeable. You can find examples of using the authorization flow in the Java SDK here. You can find an example of using a credential with a client to make call…

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

1. No, Dropbox doesn't offer a way for user to define their own APIs. 2. No, this doesn't depend on the type of Dropbox plan. The Dropbox API doesn't offer the ability to interact with Dropbox Paper templates or shortcuts programmatically, but I'll pass this along as a feature request. I can't promise if or when that might…

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.