Comments
-
The "request body: could not decode input as JSON" error should indicate that the value you're sending in the request body couldn't be successfully parsed as JSON. In this case, that should be the value you have in the "data" field. Looking at that value, it seems the issue is that you have an extra \" at the end in \"\".…
-
@"Lansend" I don't have any news on this request, but thanks for the note!
-
Thanks for the additional information. That's helpful. The extra portion you're seeing on the access token is a region suffix, which Dropbox will append in certain cases. The access token is still meant to be opaque, so the app should still just use the access token string as provided, including that suffix, if present.…
-
An access token shouldn't be immediately invalidated like that. It sounds like the access token string itself is somehow getting corrupted somewhere in the process. For reference, it sounds like you're getting an 'invalid_access_token' error, indicating that the supplied access token isn't valid. This indicates that the…
-
It is not possible to fully automate this process. This needs to be done manually by the user at least once. If your app needs to maintain long-term access without the user manually re-authorizing it repeatedly, the app should request "offline" access so that it gets a refresh token. The refresh token doesn't expire and…
-
@"Jay0203" Здравко is correct; changing an account's password does not affect any app keys, app secrets, access tokens, or refresh tokens for that account. Those can all be managed separately, e.g., via the App Console or Connected Apps page.
-
@"GIS_questions" As Здравко referred to, I recommend using the official Dropbox JavaScript SDK if possible, as it will do much of the work for you. Alternatively, it may also just serve as a good example even if you can't use it.
-
It looks like you're attempting to use a refresh token as a "Bearer" token in a few places in this case (where you set the "Authorization" header to "Bearer" + refreshToken). Refresh tokens themselves are not access tokens and cannot be used as Bearer tokens though, so please update your code to remove that. Refresh tokens…
-
This is now possible using the SearchOptions.account_id field on the /2/files/search_v2 endpoint.
-
Thanks for opening the ticket with the additional details. We'll follow up with you there shortly.
-
I just tried this out, and this functionality is working properly for me. Can you clarify what you mean when you say you've "verified the path that we are trying to access"? Also, I see you've redacted the path value anyway. If you'd prefer to share the troubleshooting details privately, you can open an open an API ticket…
-
Can you also share the options you're sending for the call, as well as show how you've "verified the path that we are trying to access"? Thanks in advance!
-
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…
-
Adding a scope to your app via the App Console does not retroactively grant that scope to existing access tokens. That being the case, to make any API calls that require that scope, you'll need to get a new access token with that scope. You can retrieve a new access token the same way as you would have originally, either…
-
Based on the URL of the Dropbox web site you shared, it seems like you're looking at your "team space". The API calls would be operating relative to your "member" folder by default, so you won't see the new files/folders in your team space by default. You'll need to look in your member folder instead. Your member folder is…
-
There haven't been any recent changes to the API that should have caused uploads to stop working. Can you print out and share the response you get from the API? If it's not an error, it should contain the metadata of the uploaded file or created folder. Also, how/where are you checking for the new file/folder? If you're…
-
@"zsiwik" As Здравко said, you get an app key and secret for the Dropbox API by registering an app here. You can find the developer terms here.
-
@"mikesam" My first post in this thread was from several years ago, so some things may have changed since then. You can find the latest resources for the .NET SDK here. If something isn't working as expected, please share the details, such as the steps you're following and the code you're running, so we can take a look.
-
@"Omri1984" It looks like our comments just crossed. Please refer to my previous comment for information. If you configure that as described there, you do not need to call RefreshAccessToken yourself.
-
@"mikesam" As Здравко mentioned, it's not recommended to distribute any access tokens for your own account to other users. You can technically now use scopes to restrict an app/access token to only have read and not write access, but it still would be a bad security practice to distribute your access token(s). You may be…
-
@"Omri1984" Здравко is correct; the SDK can handle the refresh process for you automatically, but you need to supply the refresh token, and app key, and if not using PKCE, the app secret. In your code, you're only supplying an access token. You can find an example of getting and using a refresh token in the OauthBasic…
-
@"Melisek" For the 400 error, please share the full error message as well as the relevant code snippet.
-
@"Melisek" That indicates that the redirect URI you're supplying when exchanging the authorization code doesn't match the one used to retrieve it originally. Make sure you're supplying the same redirectUri value to both GetAuthorizeUri and ProcessCodeFlowAsync.
-
@"Melisek" An 'invalid_grant' error typically indicates an misconfiguration of the parameters for the OAuth flow, such as an incorrect authorization code, mismatched redirect URI, etc. You should be able to get a more specific error message like this: try{ // ... your ProcessCodeFlowAsync call ...}catch (OAuth2Exception…
-
@"donaldp" Unfortunately it's not clear why that is occurring for you. I just tried and I am able to catch the expired_access_token Exception from a GetCurrentAccountAsync call when made with a DropboxClient with an expired short-lived access token and no refresh token. I can't offer much insight with .NET or C# itself,…
-
Images are included in the exported HTML, via an <img> element.
-
@"Melisek" Thanks for pointing that out! I'll ask the team to fix that up.
-
The redirect URI you use (if any) is up to you as the developer. It is intended to be a URI you control, but you can choose whatever is appropriate and functional for your scenario. It's not clear how you're accessing the authorization code on the redirect URI if you don't control the redirect URI though, since that URI is…
-
Thanks for following up. I'm glad to hear you got this working, and thanks for the feedback!
-
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…