Greg-DB Dropbox Community Moderator

Во-первых, обратите внимание: всякий раз, когда вы получаете подобный ответ об ошибке, например, с кодом ошибки 400, обязательно проверьте тело ответа, поскольку оно может содержать более полезное сообщение об ошибке. Однако, глядя на ваш код на основе вашего «refresh_token: accessToken», похоже, что вы предоставляете…

Based on your description, such as creating the app and registering the domain, it sounds like you've tried to set up the Dropbox Embedder. The Dropbox Embedder is a way of displaying content from a Dropbox shared link directly on a third party site. You mentioned that you don't actually want to display the contents…

@"Carter57" Здравко is correct. This error occurs when attempting to connect an app with any "team" scopes but the user account isn't a team admin. The "team" functionality can only be used by Dropbox teams, and can only be authorized by Dropbox team admins. If your app only needs to use "user" endpoints, such as for file…

@"athithan" That's correct, the SDK hasn't been updated to include that property yet. I'll ask the team to update it, but I can't guarantee a timeline for that.

@"dbmt" As Здравко indicated, you would need a refresh token to maintain long-term unattended access. Dropbox issues short-lived access tokens, which expire after a few hours, and optional refresh tokens, which don't expire. Apps can get long-term access by requesting "offline" access, in which case the app receives a…

No, a redirect URI is not required to get a refresh token. Whether or not a redirect URI is used though, the manual authorization step does need to be handled by the user manually in order to authorize the app to access their account and receive a refresh token. This only needs to be done once per account though; the…

The redirect URI is the location where the user should be sent after they authorize the app to access their account. It should be a URI controlled by your app and defined by you as the developer of the app. That being the case, I can't tell you exactly what yours should be, but for example, if you're building a web app and…

Dropbox is no longer offering the option for creating new long-lived access tokens. Dropbox is now 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…

@"julio_diniz_perdigao" There isn't webhook functionality specifically for /2/files/save_url jobs, but webhooks would be sent for files added via /2/files/save_url in a connected account just like files from any other source. To check the status of any particular /2/files/save_url job, you should poll…

@"julio_diniz_perdigao" The documentation for /2/files/save_url is correct; the limit was changed from 5 minutes to 15 minutes in 2023.

@"lanceuep" Thanks for the feedback!

Thanks for the feedback! I'll send it along to the team.

You can use the refresh process (that is, calling /oauth2/token with grant_type=refresh_token) to get a new short-lived access token using a refresh token at any time, but doing so does not invalidate previous short-lived access tokens. You can use /2/auth/token/revoke to revoke an access token, but that will also revoke…

@"Jeff B.63" Dropbox issues short-lived access tokens which expire after a few hours. Apps can get long-term access by requesting "offline" access, in which case the app receives a "refresh token" that can be used to retrieve new short-lived access tokens as needed, without further manual user intervention. Refresh tokens…

@"Jeff B.63" I see you have changed the parameter data to be JSON, but you still have it in the "Queries" section for your client. I can't offer support for your client itself, but it appears your client sends that as URL parameters. That JSON needs to be sent in the request body, so you probably need to put that in the…

@"Jeff B.63" It looks like you are supplying the "path" parameter as a URL parameter; it instead needs to be supplied in JSON in the request body. You can find more information in the documentation for the /2/sharing/create_shared_link_with_settings endpoint, as well as the documentation for the RPC format it uses. You can…

@"Jeff B.63" Здравко is correct; while the 'User-Agent' value is meant to contain the app's name, it does not impact the functionality of the API call. If the call is still not working for you, make sure the app is formatting the request correctly. It may help to print out the actual HTTP request, if possible. (If you…

Regarding the iOS display issues, since the content is there, albeit not displayed properly, it sounds like the shared link itself is working in that it is returning the file data. We can't really offer help with the display of content on web pages, as it looks like that would be more of a matter of HTML/CSS. As for the…

@"jonokivex" No, unfortunately I don't have news on this yet.

@"shamilto2000" It looks like you are getting a different error than the one reported in the thread you originally posted in, so I've moved your message to this thread which has the same error you're getting. Please check out the earlier messages in this thread for ways to handle loading both scripts.

No, unfortunately the Dropbox API doesn't offer a way to retrieve error logs or timing information 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 users are having trouble using shared links, I suggest reaching out to user support.

The /2/files/download and /2/files/list_folder endpoints use different formats, so those wold need to be implemented differently and so aren't a good comparison. The /2/files/list_folder endpoint is an RPC style endpoint, meaning that it requires the parameters JSON in the request body. The error message you received…

@"REL_IT" Dropbox itself does not add a "tmp" folder in your Dropbox paths. When uploading via the Dropbox API, the third party app specifies the desired destination path via the "path" parameter that it sends to the API. If you're seeing unexpected path components, please check the "path" parameter that your app is…

Based on this code, it looks like you're not formatting this HTTP request correctly: * Make sure you're using the POST method (i.e., not GET) * Send the parameters as application/x-www-form-urlencoded data in the request body, not as JSON in a Dropbox-API-Arg header * When sending the app key/secret in the Authorization…

@"REL_IT" Dropbox refresh tokens don't expire automatically, so you should store and re-use them. If you didn't store your refresh token, you'll need to process the authorization flow again to get another one. For reference, Dropbox is no longer offering the option for creating new long-lived access tokens. Dropbox is now…

@"mikechiu" Thanks for following up. I'm glad to hear this is working now. As for the rate limits, we don't have specific rate numbers to share, but you may see responses like this at any time so make sure your app is always able to catch and handle such responses.

Thanks for following up. Can you please share the rest of the requested information so we can look up these errors? Thanks in advance!

@"REL_IT" 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…

@"mikechiu" It looks like you're hitting the rate limiting system; as Здравко noted you can check the response body for the error message. Please try again after the delay and let us know if you're still seeing this issue.

@"Takashi Homma" Thanks for the context. The Dropbox API doesn't offer a way of constructing those non-shared web site URLs, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though.