Greg-DB Dropbox Community Moderator

@"Dinesh K" Здравко is correct, you'll need to make sure you're passing valid JSON in the request body for this call. We generally recommend using a JSON library to build that JSON to make sure it's valid. You can also use the API Explorer for testing/prototyping such calls.

Update: the Dropbox Saver should now work in Chrome on iOS.

Update: the Dropbox Chooser should now work in Chrome on iOS/iPadOS.

It's not possible to exchange a long-lived access token for a refresh token, however it is not necessary to make existing connected users switch anyway. Existing long-lived access tokens can continue to be used, as we don't currently have a plan to disable existing long-lived access tokens. (If that changes, we will of…

Thanks for the report! I'll ask the team to look into it.

Thanks for the note. This is open with engineering. I'll follow up here once I have news.

Are you using an app key for an app that hasn't been migrated to scopes yet? This can occur if so. (Apologies for the unhelpful error message!) In order to use the updated app authorization flow, you'll need to use an app key for an app that is set to use scopes. You can migrate an existing app to scopes via the app's page…

The Dropbox API doesn't offer a way to detect the presence of other users potentially editing a file via the API at the same time, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. Check out the Detecting Changes Guide for ways to detect when changes have been…

@"Bamante" It sounds like dsagal is referring to the browser's console, sometimes called the JavaScript console. (Refer to your particular browser's documentation for information on how to access it if you wish.) On a page where the Embedder is currently failing, that console is currently showing some errors. We're looking…

Thanks for the report! We'll look into it and follow up here with updates.

It's not clear if those settings mean that Invoke-RestMethod will use TLS 1.2. I can't offer help specifically for Invoke-RestMethod as it's not made by Dropbox, so I recommend referring to its documentation for information on configuring it.

Can you elaborate on what you mean when you say "the PCs are running TLS 1.2"? Can you check if 'Invoke-RestMethod' in particular is using TLS 1.2 for these network requests? The Dropbox API servers do currently only support TLS 1.2, so it would be fine to enable only TLS 1.2 client-side for this as far as the Dropbox API…

The 'Microsoft.PowerShell.Commands.WriteErrorException' error type isn't made by Dropbox, so I can't offer too much insight on that. If a Dropbox API call fails, the Dropbox API would return a response body, but I don't see one here. I do still expect this is related to the TLS change though, so I recommend looking into…

@"Tech Dev Oldsmar" Thanks for pointing that out! I'll ask the team to improve that example.

@"Tech Dev Oldsmar" It looks like you have the right idea here; you're grabbing the Retry-After from 'e.ErrorResponse.RetryAfter'. (Exactly how you structure your app with respect to exception messaging and thread handling is up to you though. E.g., it seems like in your sample you wait and then re-throw the exception.) I…

Thanks for the report! We'll look into it and follow up here with updates.

Thanks for the report! We'll look into it and follow up here with updates.

@"production_tvox" Здравко is correct; retrieving new long-lived access tokens is no longer an option. Refer to their message and the thread they linked to for more information. By the way, I just checked and I see that your support ticket #16503714 did get a response with information about this. If you did not receive…

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 you are using * a sample of your "ver" variable, if you can share it publicly, or otherwise a redacted version showing the hostname at least * the…

Thanks for following up. I'm glad to hear you got this working already. For reference, it sounds like you're using an app key for an app that hasn't been migrated to scopes yet. This can occur if so if you request scopes. (Apologies for the unhelpful error message!) In order to use the updated app authorization flow to…

@"Danut" A TLS issue would fail earlier in the connection process, with a different kind of error. 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…

@"Mostafa Ezzat" I see Здравко very helpfully offered a detailed walk-through of this flow. Please let us know if this still isn't working for you.

I see you're getting an error "Could not create SSL/TLS secure channel.". That confirms that this is happening because Dropbox recently retired support for TLS 1.0 and 1.1. The Dropbox API servers now only support connections using TLS 1.2. You'll need to update your app/network client/environment to use TLS 1.2 in order…

The REFRESH_TOKEN value should be the 'refresh_token' returned by /oauth2/token when you called /oauth2/token with 'grant_type=authorization_code'. That's different from the 'access_token'; the two are not interchangeable.

The authorization code can only be used once. Once you use it to get an access token and optional refresh token by calling /oauth2/token with 'grant_type=authorization_code', you can throw away the authorization code and store and re-use the access token and optional refresh token instead. You can use a refresh token to…

Whenever you make an API call, such as to /2/files/upload like in this code, you would either get a response from the API (such as the result or some API error), or some error from your network client if the connection failed. I understand you're not getting an error message in the output, so you may need to debug this or…

Dropbox doesn't offer a step by step tutorial for this exactly, but perhaps you can elaborate on what you need to do at a high level, what you have so far, and what exactly isn't working. For instance, in your first post you mentioned you needed to update your app from TLS 1.0 to 1.2. Does that mean you already had some…

I see you're not setting a redirect_uri on /oauth2/authorize, so you should also not set a redirect_uri when calling /oauth2/token. Remove that '-d redirect_uri=...' from your /oauth2/token call and try again. By the way, as a matter of security, do not post your authorization code or app secret.

This appears to be a follow up to your earlier thread. I'm afraid I don't have much to add to that. All of the official resources for using the Dropbox API from .NET are part of the official Dropbox .NET SDK, but it sounds like that SDK isn't suiting your needs. (You can of course call the Dropbox API HTTPS endpoints…

Thanks for following up. Unfortunately in this particular case this doesn't appear to be sufficient for me to investigate. Can you please open a ticket here from the affected account, and also let us know the relevant app name, so we can look into this internally? Thanks and apologies for the bother.