Greg-DB Dropbox Community Moderator

Yes, the shared link expiration functionality is only available to paid accounts, both in the API and UI.

We haven't officially announced a specific time for the shutdown, but it will likely be some time around 10 am PDT.

No, unfortunately I'm not aware of a workaround for this.

Hi Pete, I just tried your code (commenting out the 'Common', etc. lines) and it worked correctly for me. I.e., fileContents wasn't nil. What version of the SDK do you have installed? There was a bug like this in an older version. If you don't have the latest version, currently 3.3.2, please update to that and let me know…

There isn't a limit on the number of redirect URIs you can add, but I can't promise that won't change in the future.

To use the Chooser, you need to register your domain(s) as "Chooser/Saver domains", not "OAuth 2 redirect URIs". The latter is unrelated to the Chooser. If you don't register your Chooser/Saver domains, you'll get the "Origin does not match any app domain" error. Based on your sample, you should register…

I'm not sure I understand your question. Can you share a sample API request and response that is giving you trouble? (Just be sure to redact the access token.) Thanks in advance!

If you don't see your app(s) listed on the App Console, that means you're not signed in to the account that owns the app(s). You'll need to log out and then log back in to the account that does own the app(s). The /1/oauth/request_token endpoint gives you an OAuth 1 "request token", but the /2/auth/token/from_oauth1…

Thanks for the report! This is a known issue when using these links in Internet Explorer, but I don't have a timeline for a fix to offer. It's possible it's a bug in Internet Explorer itself, since it doesn't occur in other browsers. I'll follow up here with any news on this.

Unfortunately there isn't a good way to catch these errors, but I'll pass this along as a feature request.

You can choose whatever redirect URI/port you want, but whatever you do choose, you need to pre-register it on the App Console.

I'm afraid I'm not sure I follow. Generally, there should just be a single redirect URI, which is specific to your app and should be supplied by your app in the 'redirect_uri' URL parameter, and not in the 'state' parameter. Can you share a sample that shows the problem you're running in to?

Thanks for following up. The API doesn't offer the ability to append like that unfortunately. I'll pass this along as a feature request.

Thanks! I've commented there.

Exactly how you do this will depend on your setup, but in general you can download the thumbnail data from the Dropbox API to your server, and then just serve that data out normally as an image.

You can use an OAuth 2 redirect URI including a port number, but it will still need to exactly match one of the OAuth 2 redirect URIs that you previously registered, including the port and path. If they don't match exactly, you'll get the error above. So, first register the exact OAuth 2 redirect URI on the App Console…

Can you share the full exception/stack trace?

If you're using Java, we do recommend using the official Dropbox API v2 Java SDK. There's an example of uploading files included, for both uploading small files, as well as uploading larger files using upload sessions. To clarify though, do you need to append data to an existing uploaded file? Note that you can append to…

@"jczorkmid" No problem, I see your ticket now, so we'll follow up there. Thanks!

I don't have any news on this yet. I'll follow up here once I do.

Thanks for the feedback! I don't believe we've published any numbers on webhooks usage, so I'm afraid I can't offer a good idea of how common Drpobox webhooks integrations are.

Yes, using the "Generate" button to get an access token for your app-user pair would automatically link your account to your app, if it wasn't already. For end-users, your app should send them through the OAuth app authorization flow to link the app: https://www.dropbox.com/developers/reference/oauth-guide…

It looks like our comments just crossed. I'm glad to hear you got this working. It sounds like it was just that you didn't have your account linked yet.

Hi Nicolae, I just checked and webhooks are working properly for me. There are a few things to note though: - Webhooks will only be sent for users that are linked to your app. Make sure you connect your account to your app before testing webhooks. - Webhooks will only be sent for file/folder changes in linked accounts.…

@"DrMDodd" The 9/28/17 date is still the planned date for the API v1 retirement. The timeline can be found in the blog post here. We are reviewing requests for extensions on a case by case basis though. If you need an extension, please open an API ticket and include: * The app key(s) for the app(s) you need an extension…

I don't currently have a solution to offer for this on API v2 unfortunately. I just replied to your ticket though and granted your app an extension. Please check the reply there for details.

That's the old API v1 documentation. I've updated my answer with the API v2 link. Thanks!

Thanks for the report! First, for reference, we highly discourage embedding calls like this into HTML pages, as you're exposing the access token. A malicious visitor to the page could extract the access token and access the account via the API. (You should revoke the one you used on that JSFiddle.) Anyway, I'll ask the…

Thanks for the post! I've added your vote to the request to increase this timeout, but I can't promise if or when it would be changed. (I'm not aware of any immediate plans to change it.)

Unfortunately it's hard to say off hand what may be happening here. Can you add some logging to see exactly what calls the app is making and what responses it's receiving in both cases? If you can share that, we may be able to offer more insight. (If you'd prefer to share privately, feel free to open an API ticket with…