Greg-DB Dropbox Community Moderator

Dropbox doesn't currently offer OpenID Connect, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though.

Getting an access token always requires some sort of user interaction initially, either via the "Generate" button on the app's page on the App Console (when just getting an access token for the app owner's account), or via the OAuth app authorization flow (which can be used for any arbitrary user, not just the app owner).…

@"FrancoisNOYEZ" Здравко is correct, under the new system you do not need to interact with your script every time it runs. You can supply it the refresh token like you previously supplied it a long-lived access token and it will automatically run without manual user interaction, as before. You do need to process the app…

Your curl client appears to be trying to interpret each "\" character as a separate host, when those are supposed to just be characters to continue the command on a new line. I don't know exactly what shell you're using, but for the sake of simplicity you can take out the "\" characters and new lines, so the entire command…

The Dropbox API does have a general rate limiting system that applies to all account types, but we don't have any specific numbers documented. It operates on the basis of calls per period of time. It generally works on the scale of seconds to minutes though, not days to months. Also note that not all 429s and 503s indicate…

There isn't a way to force an access token to expire soon or immediately, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. So, to test the actual 'expired_access_token' error for any particular new short-lived access token, you would need to wait four hours. (You…

It looks like you're referring to some of the code included in the Android example for the official Dropbox API v2 Java SDK. I recommend running that example as provided and documented first, if you haven't already, to see how that works. To answer your question specifically though, the "Callback" in "private final…

@"Rosen Petrov" It is not possible to get authorization to access an account purely via a background process. Authorizing an app requires manual user interaction the first time, for the user to indicate to Dropbox that they want to allow the app to access their account. After that though, the app can store and re-use the…

Unfortunately this hasn't been implemented on the API. It still only supports retrieving 100 revisions. That's still open as a feature request though. Apologies I don't have better news for you!

[Cross-linking for reference: https://stackoverflow.com/questions/67035156/can-i-upload-larger-files-1gb-to-dropbox-via-dropbox-token-but-without-setting ] @"Mubasher" Здравко is correct, the issue is that the /2/files/upload endpoint only supports files up to 150 MB. For larger files, you'll need to use upload sessions…

@"RosenPetrov" The examples you linked to are the current samples for implementing the OAuth app flow with the Dropbox .NET SDK. Are they not working for you, or can you clarify what you're stuck on?

No, such apps are not forced to have the user re-authorize every four hours. Client-side apps like this can request "offline" access to get refresh tokens if needed. There's an example of requesting offline access from a client-side app (a front-end browser app, in this sample) using the official Dropbox API v2 JavaScript…

The second screenshot shows an app using a legacy non-scoped permission, which is being phased out. The first screenshot shows a scoped app, which offers more granular information and control over the permission being requested. It is not possible to revert a scoped app to a non-scoped app. The best practice is to request…

You can use the API to list the files in any folder in the connected account, whether or not the folder is shared. I recommend reading the File Access Guide and Team Files Guide for reference. Looking at your code, there are a few things to note: * You are not guaranteed to get everything back in one call to…

It sounds like in your case you've only manually generated an access token to connect to your own account, and are not using the actual OAuth app authorization flow. Long-lived access tokens are now considered deprecated, but we don't currently have a plan to disable existing long-lived access tokens. (If that changes, we…

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

Dropbox doesn't offer a way to perform operations automatically based on the age of an item, but you can use the API to write code to perform whatever operations you want, whenever desired. For example, with the Dropbox Python SDK, you can list files/folders using files_list_folder and files_list_folder_continue, and you…

No, whether you write a script to copy the files over using the API, or use the Dropbox Business feature, the files need to be put in some account.

Apologies for the confusion. When uploading files, you won't see the property information returned in the metadata directly. (I'll pass this along as a feature request though.) To retrieve it, you'll need to call getMetadataBuilder to get a GetMetadataBuilder, and then use GetMetadataBuilder.withIncludePropertyGroups to…

@"James_T" Yes, /2/sharing/create_shared_link_with_settings requires one call per item, so if there's a significant number to process, that would take a significant amount of time. That being the case, you could also consider only creating the shared link on demand, when the user clicks on a specific file. That is, the…

I see you've also opened a support ticket for this. We've followed up with you there to get some more details so we can check on this specifically for you. Thanks!

Thanks for following up. The Dropbox Saver is built to accept a URL from the third party app, and then prompts the user for where in their Dropbox account they want to save the linked file. When the user does so, the Dropbox servers then retrieve the file from the supplied URL and save the resulting data to the user's…

The Dropbox API doesn't offer a way to do this automatically, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. You could effectively reproduce this behavior though, at least within an account. To do, you'd need to do something like this: * Use…

I'm not sure I understand your question. Can you clarify? The Dropbox Saver is a way for third party apps to give files to users that they can save directly to their Dropbox accounts. You can find all of the information on the Saver here. Alternatively, if you want the opposite flow, where a user selects a file from their…

No, unfortunately this isn't available on the API, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though.

The location within the account doesn't really matter, but which account it is in does matter. From your description, it sounds like the file is not in the connected account (that is, the account for the access token you're using), but rather is in another account (and the file just happens to be shared individually to the…

Thanks for clarifying! The Dropbox API doesn't offer the ability to search/list files with names containing a certain prefix in particular, but you could use the /2/files/list_folder[/continue] and/or /2/files/search_v2 endpoints to list or search for files, and filter the results client-side as desired.

Dropbox itself doesn't offer a way to set a size limit on a shared folder like this, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. If you're implementing this on your server though, you could enforce the limit there. That is, have the user upload to your server,…

@"ygnmax" We don't have anything built specifically for S3 like this, so if you're a programmer and want to write something to do this, the method in my previous comment would probably be a good option to use.

I see, thanks for clarifying. No, that wouldn't explain /start failing, since /start itself returns the session ID to begin with. I happened to be testing in Firefox, where the /start call did work successfully for me (and still does). Trying in Chrome now though, I can reproduce this issue. I'm not sure exactly why this…