Greg-DB Dropbox Community Moderator

It sounds like your team now uses the "team space" configuration. You can access the team space via the API, but you'll need to set the 'Dropbox-API-Path-Root' header to do so. You can find information on this in the Team Files Guide.

Unfortunately Dropbox doesn't currently have an example like this for UWP posted, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though.

The "redirect_uri mismatch" error indicates that this call failed because the redirect_uri used on /oauth2/authorize to get that authorization code does not match the redirect_uri used when calling /oauth2/token. These two values need to match exactly. Or, if you didn't set redirect_uri on /oauth2/authorize, you should…

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…

The "Access to a closed stream is not possible" error message doesn't appear to be coming from the Dropbox API itself, so I can't offer too much help with that in particular. That said, it's likely referring to that "memStream" object. It looks like that's closed, since it was used in the first attempt, so you'd need to…

We don't have video tutorials for the API/SDKs, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. The "LoopbackHost" in the example is the address of a local server, defined by the app, used for the redirect URI for the OAuth app authorization flow. That's where the…

Thanks for the report. Can you share several X-Dropbox-Request-Id values for these failures? They're safe to share publicly, but you can open an API ticket here if you'd prefer to share privately.

No, Dropbox no longer offers the option for retrieving new long-lived ("no expiration") access tokens. You can find more information on this migration here. Instead, to get long-term access, apps should request "offline" access, in which case the app receives a "refresh token" that can be used to retrieve new short-lived…

In the code snippet you shared, "authorize" and "token" are just strings used as URL paths on the local server used to handle the result of the OAuth app authorization in that example app.

I see, thanks for the context. That expiration only applies to the access token. You can find more information on each field in the documentation here.

No, the Dropbox Chooser does not offer an option for getting the name of the parent directory of the selected file. You can find all of the available options in the Chooser documentation.

@"marksmithhfx" It looks like the use of POST for these requests is required in the OAuth 2 specification: The client MUST use the HTTP "POST" method when making access token requests. I'll send this along as a feature request to support GET as well, but I can't promise if or when that might be implemented (especially as…

[Cross-linking for reference: https://stackoverflow.com/questions/71955472/how-do-i-automate-retrieval-of-a-refresh-token-using-the-dropbox-python-3-x-api ] Dropbox API refresh tokens do not expire after four hours. They can be revoked on demand, but they do not expire automatically, and can be stored and re-used…

Dropbox offers the official Dropbox API v2 .NET SDK here: https://github.com/dropbox/dropbox-sdk-dotnet There are instructions for that here: https://github.com/dropbox/dropbox-sdk-dotnet#readme And examples here: https://github.com/dropbox/dropbox-sdk-dotnet/tree/main/dropbox-sdk-dotnet/Examples For instance, this example…

Yes, any change at all will count as a write, such as adding, editing, moving, copying, sharing, or deleting files or folders, by any means (such as the Dropbox API, web site, client, etc.). That will include both CreateFolderAsync and SaveUrlAsync, but not Download.

Unfortunately, the Dropbox Chooser does not have an option for retrieving "direct" links that do not expire, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. As a workaround, you can use "preview" links, which don't expire, and modify them for direct access as…

The Dropbox .NET SDK is already automatically uses the best available version of TLS, though we recommend updating to the latest version of SDK in general as a best practice, if you haven't already. The latest version of the Dropbox .NET SDK is currently v6.26.0. While the Dropbox SDK itself will use the best available TLS…

Can you elaborate on what you mean when you say "it doesn't work"? What unexpected error, output, or behavior are you getting? I recommend stepping through with the debugger first to see what is being executed and when to understand what is happening.

The Dropbox API will save whatever data you supply in the HTTPS request body for the upload call as the file data, so you'll need to make sure you're sending the exact correct binary data that you want to store. In the code you shared here, that seems to be your "data" variable. Make sure that variable contains the data…

Thanks, that error indicates an issue establishing the TLS connection. Specifically, it looks like wget is attempting to use TLS 1.0, but Dropbox recently retired support for TLS 1.0 and 1.1. The Dropbox servers now only support connections using TLS 1.2. You'll need to update your app/network client/environment to use TLS…

The Dropbox Chooser page does include a working demo under the "Demo" section. Is that "Choose from Dropbox" button not working for you? If not, what exactly does/doesn't happen? Do you get any error message?

@"Marcos Paris" To debug this, try running this with "-v" instead of "-q". That should enable more verbose output that should help identify the issue.

While you can use either the HTTPS endpoints themselves or one of our official SDKs such as the Dropbox JavaScript SDK (or a third party library) to access the Dropbox API, we do recommend using one of the official SDKs, as they'll do much of the work for you. In the Dropbox JavaScript SDK, the corresponding method for…

I see you're calling /2/sharing/get_shared_link_file and are supplying both the "url" parameter and "path" parameter. The particular shared link you're sending as the "url" is for a file though; in that case you should not also supply the "path" parameter. The "path" parameter is only for when you need to specify a…

I see you're using upload sessions to upload files by doing so in multiple pieces. With this functionality, you can catch and handle any exceptions that may occur, and then resume the process by picking up with whichever upload session call you last made. For instance, if a particular call, such as UploadSessionStartAsync…

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…

It sounds like you'd be interested in the "file_operations" category and the "file_add" event type. You can find everything listed in the documentation here. The API v2 Explorer can also be useful for testing calls like this.

@"chek534" Make sure your platform itself also supports TLS v1.2. Some platforms/frameworks, especially older versions, may not have TLS v1.2 enabled. You may need to refer to your platform documentation for information on configuring that.

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. That…

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…