First I can't display files sent to me via a Dropbox link on Chrome. There's an example implementation with the API v2 JavaScript SDK here.Hi everyone, I'm having a strangely annoying thing go on today with Dropbox on Chrome. You can find more information on how the OAuth app authorization flow works in the OAuth guide, and the documentation can be found here. That's actually a web page that the user should be directed to though, not an API endpoint. Looking at the error in your screenshot, it looks like you may trying to call directly in your JavaScript code (e.g., via an AJAX call).

The result is an access token that the app can store and re-use to make further API calls for the user. To do so, the app should send each user through the OAuth app authorization flow in their browser. While we don't have anything specifically for Chrome extensions/Angular JS apps, I do recommend using the official Dropbox API v2 JavaScript SDK if you can.Ĥ. The API was designed with the intention that each user would link their own Dropbox account, in order to interact with their own files. The redirect URI for your app is specific to your app, and would depend on your app's setup, so I can't say off hand what it should be for your app.ģ. We don't have any specific resources for Chrome extensions/Angular JS in particular, but the API itself can be used anywhere you can make HTTPS calls.Ģ. E.g., have them click on the link as shown in the example, or redirect them via JavaScript, such as using (url) or .ġ. You instead need to send the user to that page as a normal navigation operation. In your code, you're attempting to make a GET request to the /oauth2/authorize page. Production status just removes the limit on the number of users that can connect to your app. I recommend trying the example to see how it works.

No, the user does not need to register their own API app. Your app uses its own app key to send them though the OAuth app authorization flow. If you omit it, the user just needs to copy/paste the authorization code into your app.)Ĥ. (Also, if you use the 'code' flow, the redirect URI isn't strictly required. I recommend reading the OAuth guide for context on how the flow works.

I can't offer guidance on how to build a Chrome extension in particular, but I know Chrome extensions sometimes use 'chrome-extension://' URLs for their option pages, so you may want to look into that.

Regardless of the type of app, the redirect URI would be the URI where you want to send the user back to after they approve your app to access their account.

Dropbox downloader chrome