Greg-DB Dropbox Community Moderator

We don't currently have any documentation for the app authorization flow built in to the official Dropbox mobile apps, but I'll be sure to pass this along as a request for that. That flow is handled for you in the SDKs, but if you're not using one of the SDKs, we do recommend using the standard OAuth flow in the browser as…

The modification Dave suggested will cause Dropbox shared links to return the file content itself (instead of a preview page), but note that for your code to work with that it will need to follow redirects. You can find the full information here: https://www.dropbox.com/help/201

If you're a programmer, you can use the Dropbox API to connect to your Dropbox account. Otherwise, you'll need to use an integration built for Magento by a third party. Unfortunately I can't support or endorse any in particular though.

That's correct, CORS isn't enabled on www.dropbox.com. The parameters ( dl or raw ) are preferred, but if they don't suit your use case, one alternative is to change host from www.dropbox.com to dl.dropboxusercontent.com, that is: www.dropbox.com/s/... to: dl.dropboxusercontent.com/s/... CORS does work on the latter…

Yes, there's information here on modifying the links from /shares for different behaviors, e.g., to return raw content: https://www.dropbox.com/help/201

Yes, you can use the /shares endpoint to get a shareable link to a file or folder: https://www.dropbox.com/developers/core/docs#shares

You're using OAuth 1 with HMAC-SHA1 signing, which is prone to issues like this. We highly recommend using PLAINTEXT signing instead, as it's much easier to implement and debug: https://blogs.dropbox.com/developers/2012/07/using-oauth-1-0-with-the-plaintext-signature-method/ Try that and let us know if that doesn't help.…

First, to clarify, when you say the access token is "gone", do you mean that it is just no longer displayed on the App Console, or that your API calls using it start failing? The former is expected, e.g., if you leave or refresh the page. The generated access token is only displayed to you when it is generated. It doesn't…

Hi Alex, Dropbox doesn't offer an embeddable version (and I'm not aware of any such immediate plans), but I'll send this along as a feature request.

For reference, this was fixed here: https://github.com/dropbox/SwiftyDropbox/commit/8fc2eed6f05af8a27a37cf76c244a0b56b065d85 That change should be included with the next release.

Thanks for confirming that! We're working on it.

Is that the actual file name, or have you redacted the part before the extension for privacy reasons? We've been able to reproduce this issue when there are unicode characters in the filename, but we'd like to verify if that is or isn't the same case you're seeing.

Hi Eric, it looks like you started a new thread for this, so I'll reply there: https://www.dropboxforum.com/hc/en-us/community/posts/213302606-Get-notified-if-webhook-is-disabled

I can't make any promises of course, but I'm sending this along as a request. Thanks!

Unfortunately, the Dropbox iOS Core SDK doesn't provide any background support for you. It's mainly just a wrapper around calling the Core API HTTP endpoints. It also doesn't use NSURLSession. That being the case, if you need background support you'll need to implement that into your app using Apple's standard background…

Have you checked your code for disable_access_token or disableAccessToken though? (The latter is the method in the Java SDK that calls the /disable_access_token endpoint.)

OAuth 2 access tokens for the Dropbox API don't expire, as you said, but they can be revoked: * by the user revoking the app on the account security page * by the user deleting the app folder (if the app uses the app folder permission) * by the app calling /disable_access_token Do any of these apply to your app? E.g.,…

You're getting this on the webAuth.finish line, right? This error indicates that the authorization code you're using is invalid or expired. (These authorization codes currently expire after five minutes.) You should use the authorization only once, immediately after receiving it. After that, you can store and re-use the…

When you register an app, it won't automatically be linked to your account. You need to authorize it to access your account, like an end-user would. I recommend working through the tutorial for the SDK or library you're using (if any). The OAuth guide may be helpful too.

Linking to the other thread where this was also asked, no update right now.

That's not currently available, but I'll be sure to pass this along as a request.

No update on this.

Unfortunately I don't know if/when this may be added to API v2.

Hi Julian, I imagine that's a typo and you meant to say that "SwiftyDropbox is only capable of accessing API v2". Anyway, it's not possible to use SwiftyDropbox to access API v1. If you wanted to though, you could technically use API v1, either via the HTTP endpoints, or the iOS Core SDK. Note that API v1 is deprecated…

To clarify, this is currently available in API v1, but not API v2.

This isn't currently available in API v2, but I'll be sure to pass this along as a feature request.

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

Yes, email address is available via /shared_folders in the Core API: https://www.dropbox.com/developers-v1/core/docs#shared-folders

Hi Antriksh, the display_token page was designed for the "token" flow, not the "code" flow. You can find information on the two different flows in the /authorize documentation here: https://www.dropbox.com/developers/documentation/http/documentation#oauth2-authorize If you want to use the code flow and have the code…

This is an issue inherent to using OAuth 1 with a client-side app. If you're using OAuth 1, this is unavoidable. You can try to obfuscate the keys to make it difficult, but you can't make it impossible to extract them. If they are extracted, this doesn't itself enable access to user data though, it would just let someone…