Greg-DB Dropbox Community Moderator

@"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.

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 steps to reproduce the issue, including relevant code snippet(s), but don't include any access or refresh token(s) * the full text of any error or unexpected output * 5-10 sample…

@"Takashi Homma" It sounds like you're referring to the /home and /work routes on the Dropbox web site. The Dropbox API doesn't use those; for information on interacting with different files/folders on the Dropbox API, I recommend reading the File Access Guide and Team Files Guide.

@"skezh1" Thanks for the report. The thread you originally posted in was old, so I've moved this to a new thread. There hasn't been a new release of the Dropbox JavaScript SDK recently, and I'm not seeing this issue in my own testing now. I'll be happy to help with any issues you're having with the Dropbox API/SDK, but…

These values may encode information about the relevant account, so you may notice patterns like this, but your app should not expect or rely on any particular format or pattern. Your app should only use the authorization code as supplied. You should not attempt to decode or otherwise extract information from the…

The Dropbox API authorization functionality includes a number of different types of values, including authorization codes, access tokens, and refresh tokens. You can find the documentation for all of that here. Each of those are only specified as "String" without a more specific format guaranteed, so make sure you're not…

The raw=1 functionality itself should still work, but there's no particular guarantee on its use with an embed or iframe HTML element. You can find the official documentation for that here; that doesn't have any mention of iframe or embed. That said, when I tried the sample page you shared on iOS, it did actually show the…

You can find information on the limits for Dropbox links here.

You can use the Dropbox .NET SDK in C# to perform these calls. You can find the documentation for the corresponding methods in that SDK here.

There are technically different types of shared links, and the exact behavior of this may vary for the different types. In any case, the API doesn't offer an option to explicitly control that behavior, but you can remove a shared link on demand by calling /2/sharing/revoke_shared_link.

Yes, the Dropbox API does have several endpoints for working with legal holds. You can find the documentation for them starting here: https://www.dropbox.com/developers/documentation/http/teams#team-legal_holds-create_policy

Dropbox does offer an API you can use for listing, uploading, and downloading files, among other operations. You can find everything you need to get started with the Dropbox API, including documentation, tutorials, and SDKs here. Dropbox issues short-lived access tokens, which expire after a few hours. Apps can get…

I don't believe we have example code for using that. Perhaps you could share the relevant piece of code you have so far and show what you're stuck on (e.g., any unexpected error/output)? Be sure to redact any actual access/refresh tokens though.

The reauthorizeClient method would set the authorizedClient to use an access token that's already been stored. If you haven't stored the relevant access token, then that won't work. (The built-in OAuth functionality would automatically store the access token, but that won't occur automatically if you copied it from another…

@"mikechiu" Apologies for the trouble with the forum. It looks like your post got stuck in the spam filter. Anyway, we'll look into this API issue and follow up here once we have an update. Thanks!

@"anas saifi" As Здравко said, those "preview" shared links on www.dropbox.com point to a preview HTML page, not the file data itself, and do not support CORS. If you want to directly access the file data using CORS, you can use the "direct" link type (instead of "preview") when setting up the Chooser.

@"rashi" Здравко is correct; the Dropbox API currently only supports TLS 1.2, not 1.3, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though.

The beta mentioned above has been promoted to stable release. Read more about it here: https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Major-SwiftyDropbox-update-available/td-p/737816

The beta mentioned above has been promoted to stable release. Read more about it here: https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Major-SwiftyDropbox-update-available/td-p/737816