Greg-DB Dropbox Community Moderator

We were able to reproduce this, but I don't have an update from the team yet. The captcha usually isn't shown anyway though, and is only displayed when possibly needed, as determined by our automated abuse system, so it's expected that you wouldn't reliably see the captcha/captcha issue.

No, shared links don't offer resizing functionality.

1. Yes, this is the expected behavior. 2. In API v2, it would be a 409 with a specific error, e.g., on /files/download, it's restricted_content. In the API v2 Objective-C SDK in particular, that becomes DBFILESDownloadError.path with a DBFILESLookupError where isRestrictedContent is true.

It sounds like you're referring to the functionality provided by a third party app that uses the Dropbox API. As this is made by a third party, I'm afraid we can't offer help for it directly. You should contact support for the app itself. (If the developers of the app are having trouble with the Dropbox API, they can then…

Yes, unfortunately due to some specifics of how Dropbox is implemented, not all of the path components can be guaranteed to have the expected casing. You can find more information on this in the "Path formats" section under: https://www.dropbox.com/developers/documentation/http/documentation#formats There's also some…

The SDK uses a default URI, so it doesn't need to be explicitly provided. My third link shows where the SDK checks that the app is registered for the default URI though (db-<app_key>).

You can set the access level directly in the AddMember you use with AddFolderMemberAsync in the first place: https://dropbox.github.io/dropbox-sdk-dotnet/html/M_Dropbox_Api_Sharing_AddMember__ctor_1.htm If you need to modify a member's access level after the fact though, you can use UpdateFolderMemberAsync:…

The MountFolderAsync method takes a shared folder ID, which is the same as the sharedFolderId value from my code sample. You can also use ListMountableFoldersAsync/ListMountableFoldersContinueAsync to list the folders available to mount in an account. Your latest sample instead seems to just be getting the ID of a file,…

That's correct, you should use /2/sharing/list_shared_links and filter the results to just the files in the folder(s) you're interested in. Make sure you check the has_more field in the result to see if you need to call back for more results.

Can you share the relevant code snippet(s) and the error message you get so we can look into it? Thanks in advance! 

Yes, as long as you're authorized as the receiving user you can use MountFolderAsync to mount the shared folder in their account.

I'm afraid I can't recommend any particular third party resources unfortunately, Denis. Perhaps some other developers on the forum here can recommend some though.

The links returned by get_temporary_link aren't intended for being directly displayed in the browser unfortunately, but I'll be sure to pass this along as a feature request.

Thanks for the report! This is a known issue with how IE handles these links. The expected behavior is that the browser would download the file, based on the Content-Disposition header. IE doesn't seem to do so, and instead does nothing, as you mentioned. I'll send this along to the team, but I can't say if or when we'd be…

[Cross-linking for reference: https://stackoverflow.com/questions/40595734/exchanging-a-dropbox-authorization-code-for-a-re-useable-access-token-with-php-a ] I just posted an answer on StackOverflow, but in short, you can use /oauth2/token to exchange an authorization code for an access token:…

You're correct that the OAuth 2 implicit flow requires a redirect URI. When using the API v2 Java SDK in an Android app, the SDK automatically uses a local redirect URI, based on your app key. You can see how this works in the code:…

The Dropbox Chooser is a separate kind of integration than the Dropbox API (e.g., the get_metadata method). The Dropbox Chooser is a simple pre-built component that just allows the end-user to select a file from their account and give it to the app. You can use the Dropbox Chooser and the Dropbox API in the same app, but…

It sounds like you're referring to the Sync SDK, based on the deprecated API v1. We don't have an equivalent SDK for API v2, but I'll be sure to pass this along as a feature request. That being the case, you'll need to implement the logic for offline caching and conflict resolution in your app using the API v2 calls.…

Per the documentation, the "download_files" event is triggered when you "download files from the webapp". It sounds like you're downloading a file via the web app as the owner, which will trigger that event even if the file happens to be shared. The other events are about the downloading of shared content by another team…

You can filter Metadata objects by checking if they are FileMetadata or FolderMetadata (or DeletedMetadata) instances as shown here: https://github.com/dropbox/SwiftyDropbox#response-handling-edge-cases

To share a folder, you should first call ShareFolderAsync. That takes a "path" parameter that should be the path to the folder that you want to share. The documentation explains how to check the result of that operation. Once that's done, you should then call AddFolderMemberAsync to invite members to that shared folder.…

Good news, we now have a Paper API: https://www.dropbox.com/developers/documentation/http/documentation#paper

For reference, we now have a Paper API: https://www.dropbox.com/developers/documentation/http/documentation#paper It doesn't offer a way to embed documents, but we'll still tracking that in particular that as a feature request.

Webhook notifications should be sent for any changes in the accounts of Dropbox users that are linked to your API app, regardless of whether or not the changes are in shared folders. If you're not receiving webhook notifications when you're expecting them though, we'll be happy to look into it for you. That would likely be…

I'm afraid I still don't follow. Can you share what you have so far that's giving you trouble? For reference, API v1 supports both OAuth 1 and OAuth 2. API v2 supports only OAuth 2. You can use the same OAuth 2 access tokens across both API v1 and API v2.

In what way is it not working? What response are you getting?

Thanks! That's helpful. We'll look into it.

Thanks! We'll try that out, but please do share the screenshots whenever you can so we can make sure we can reproduce exactly what you're seeing.

When using OAuth 2 to make an API call like this, as it appears you are, you should supply the token as a "Bearer" token in the "Authorization" header. The header shouldn't go on the URL itself though, as you have. For example, using OAuth 2 with API v1 to revoke the access token, it would look like this, using curl: curl…

Thanks for elaborating. I'll have the team take a look to see if we can offer a solution.