Greg-DB Dropbox Community Moderator

@"bszt123" Здравко is correct; this error is referring to the access token being expired, not the refresh token. When you get this 'expired_access_token' error, you should use the refresh token to get a new access token. If you're using a Dropbox SDK, the SDK will do this for you automatically, as long as you supplied the…

@"Zahra1" For more information on how the authorization process works, please refer to the following resources: * https://developers.dropbox.com/oauth-guide * https://www.dropbox.com/developers/documentation/http/documentation#authorization * https://dropbox.tech/developers/using-oauth-2-0-with-offline-access While Dropbox…

Thanks for the context!

@"sundares80" I will follow up here with any news on this, but again just to be clear, at this point I cannot say if the team will or won't be deploying any changes for this.

Thanks! I'll ask the team to fix that up.

Thanks for sharing that. From your earlier screenshot, I see that the app is registered for the redirect URI "dbssample://LoadPDFFromURL.UWP/", however in the 'redirect_uri' parameter in this authorization URL, I see that you're using "dbssample://loadpdffromurl.uwp/". Those values need to be exactly the same. So to…

Unfortunately there isn't an API call to completely unlink an API app, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. Users can unlink apps via https://www.dropbox.com/account/connected_apps . Apps can revoke specific access tokens/refresh tokens using…

Can you share the full URL of the page displaying that error message? That would help for debugging this.

Yes, that error indicates an issue with the value passed to as_user. The as_user method requires a team member ID, not an email address. You can get team member IDs from team_members_get_info_v2 or team_members_list_v2 and team_members_list_continue_v2, for example.

Yes, this applies to both /2/team_log/get_events and /2/team_log/get_events/continue. In any case that you get "has_more": true, whether from /2/team_log/get_events or /2/team_log/get_events/continue, you should call back to /2/team_log/get_events/continue.

The 'events' list returned by /2/team_log/get_events and /2/team_log/get_events/continue does not have a guaranteed minimum size, and so may have a size of 0 in some cases. It may vary across calls, teams, parameter values, etc. Whenever an app receives "has_more": true it should call back to…

The Dropbox API and the Dropbox web site both use the same filesystem data, so it's not expected that you'd see a different state (e.g., deleted or not deleted) for the same item at the same time across the two interfaces. Can you double check you're looking at the same item in both places? For instance, you can call…

That error for this call indicates that this failed because the account that owns the app for that refresh token/app key/app secret is disabled. When an account is disabled, any apps owned by the account are also effectively disabled. You'll need to instead get and use a refresh token/app key/app secret for an active app…

Thanks, that's helpful. It looks like you're actually hitting a different issue now. It appears you're sending an improperly formatted Authorization header value. Please remove any leading or trailing whitespace from your access token string (self.app_token in this code snippet) and try again.

@"dwWithCat" Здравко is correct; for a situation like that, you'll need to instead follow "Programmatically creating Saver buttons" or "Triggering the Saver from JavaScript".

@"sz3324" I just wanted to follow up here to let you know we believe we've tracked down and replicated the issue here. Please refer to the post here for more information.

@"sundares80" Thanks for confirming that. I've raised this to the team to ask that they change the server to accept requests with the extra new line. Again though, please note that I can't promise if/when such a change would be deployed. I'll follow up here with any updates on that. Also, as Здравко noted, please be aware…

@"dwWithCat" I just tried this and the Saver button was successfully built and clicking it successfully launched the Saver, not a new tab showing the image: <!DOCTYPE html><html> <head> <script type="text/javascript" src="https://www.dropbox.com/static/api/2/dropins.js" id="dropboxjs"…

@"sundares80" To clarify, we have not made any changes on the Dropbox servers to address this. Здравко helpfully identified a potential cause of the problem, which is that your devices may be sending an unexpected new line at the end of the request body payload. In order to validate if that is the cause of the issue, and…

@"CD12" By default, API calls to the Dropbox API operate in the "member folder" of the connected account, not the "team space". That means that by default, folders will not be created in the team space, for example. You can configure API calls to operate in the "team space" instead though, in order to interact with…

Is that all of the actual relevant code you're running? I notice you don't seem to be using the 'root_namespace_id' value anywhere. Are you calling with_path_root? Please share any other relevant pieces of code. Also, please share several more (5-10) current error outputs like this so we can look into what you're currently…

@"dwWithCat" In order to successfully use the Saver, make sure you're configuring the attributes, etc. as documented. Please refer to my previous message for a few specifics to check to make sure you configure this correctly. Also, the Saver does support uploading image files from URLs.

Your first code snippet shows you POSTing some information to your server, not directly to the Dropbox API, so it's unclear what that does. Presumably you then have code that calls the /2/files/save_url Dropbox API endpoint. That offers essentially the same functionality as the Dropbox Saver, but using a different…

Update: we confirmed this is related to sending an incorrect root for the account; in some cases the server would return a 500 instead of the expected 422 error. We've fixed that so it should be returning the proper 422 now. Please refer to the "Path Root Header Modes" documentation for information on that.

It sounds like your team may have recently migrated to the updated team space configuration, in which case your team-owned content would now be in your team space. By default, API calls to the Dropbox API operate in the "member folder" of the connected account, not the "team space". That means that by default, the contents…

@"eni8ma" A "Basic" value used in the "Authorization" header corresponds to "App Authentication". A "Bearer" value used in the "Authorization" header corresponds to "User Authentication" (or "Team Authentication"). User (or Team) Authentication are used to access a specific user account (or team). App Authentication is…

Thanks! @"sundares80" Would you be able to modify a device you have access to in order to have it not send the additional new line as a test? If you can verify that fixes the issue, I can ask the team to look into changing the server to allow that (though please note I can't make any promises on that).

@"Здравко" I can reproduce the 400 Bad Request using your code snippet, but can you clarify how you determined that this "Bad Request" issue is the cause of the problem originally reported in this thread? I don't see "Bad Request" or "400" mentioned in this thread before. The original poster seems to have reported the…

@"crunchmasterdeluxe" A "path/not_found" Dropbox API error indicates that the API call failed because there was nothing currently found at the specified path in the connected account under the relevant root. For example, this can happen if there's a mistake or typo in the path value the app supplies, if the file/folder has…

@"Synk" Здравко is correct; the Dropbox API requires TLS (v1.2 in particular, currently), and is currently being served with a valid certificate (from DigiCert). You generally shouldn't need to configure anything manually to be able to connect to that; the default is usually sufficient. We recommend against disabling the…