Steve M. Dropboxer

https://www.dropbox.com/developers/core/docs/python#DropboxClient.share If you have a DropboxClient object called client, then it's just print client.share('/myfile.txt', short_url=False). If you're having trouble getting the DropboxClient set up in the first place, take a look at the…

What's the actual body of the 400 response? (You may have to catch a WebException or the like and then pull out the response from there.) Generally the 400 will tell you the issue. I think the issue here may be the Authorization header. You're using a lowercase b in "bearer" instead of the uppercase B in "Bearer".

To clarify for the benefit of others who read this, you can use the Chooser with any app permission (including Full Dropbox). But it sounds like you were trying to add an OAuth 2 "redirect URI" instead of a "Drop-in domain." When you add a Drop-in domain, it doesn't have any protocol at all. (E.g. you would enter just…

"Family E.", why wouldn't you just use the regular /files/upload API endpoint to do this?

Steven, are you saying there's no server-side component to this app? (You're distributing apps that get installed on people's computers?) If so, you're right that you shouldn't embed an access token in that app, just as you wouldn't want to embed S3 or FTP credentials in the app. I was assuming some server-side component…

Steven, why wouldn't you just use the Core API (/files_put) to upload the file? (Why do you need to use a file request?)

Jim, you're also interested in programmatically uploading files to an existing file request? I'd love to hear your scenario as well. If you don't want to elaborate here on the forum, feel free to open an API support ticket: https://www.dropbox.com/developers/contact.

Steven, I think I understand the use cases for programmatically creating a file request, but I haven't heard many requests yet to programmatically upload a file to an existing file request. Would you mind describing your use case?

If you call https://www.dropbox.com/developers/core/docs#metadata with the include_membership query parameter, you'll get a list of all the members of the shared folder. https://www.dropbox.com/developers/core/docs#shared-folders will return a list of all shared folders and the membership of each. Shared folder metadata…

Out of curiosity, Tilman, why do you care? Why not just sort the list once you have it?

I don't believe this relates to the Dropbox SDK. (At least I haven't heard of this issue from anyone else, and none of our SDKs use push notifications.)

Ray, your question doesn't seem to relate to this thread. Are you a developer using the API to write your own app? If not, you probably want to ask your question on the Issues & Troubleshooting forum.

No, unfortunately there's no API for albums.

Ed, I think you're in the wrong forum. This forum is for developers using the Dropbox API. The Chooser is a component used by software developers to integrate Dropbox into apps that they build. I think that Product Feedback is probably the most appropriate forum for your question. When you create a post over there, please…

Ah, maybe we should add an update to the blog post to mention that it doesn't apply to the mobile choosers (which were created later).

Update the docs in what way? https://www.dropbox.com/developers/dropins/chooser/android is the documentation for the Android Chooser, and I don't think it mentions multiple file selection at all. (In fact, DbxChooser.Result doesn't have any provision for multiple files.) Over time, we'll be updating all our samples to use…

We're already tracking this as a feature request. (As you noted, it's in the JavaScript version already.) Yes, you can build your own version of the chooser with the Core API, but users will have to go through the OAuth flow (and you'll need to build the UI yourself).

No, the mobile Choosers do not support multiple file selection.

Yes, a Dropbox for Business app with "team member file access" permission that has been linked by a team admin can read and write all files for all members of the team.

Dropbox for Business apps aren't used by individual team members. If you just want to use Core API calls on individual users, you shouldn't create a Dropbox for Business app.

Apps that use the Dropbox for Business API can only be linked by Dropbox for Business team admins. A user with a Basic account will not be able to link with a Dropbox for Business app.

Could you explain what "doesn't work" means? Do you get an error? If so, what does the error say?

Start with https://www.dropbox.com/developers.

Detailed documentation is coming as we get further along in build API v2. Nothing about the OAuth process is expected to change, though. It works the same way as OAuth 2 in the current Core API (v1).

You can theoretically do this by registering for a custom URL scheme and using that as your redirect URI, but what we recommend is to embed a web browser control in your app, as per the example I linked to.

I'm not sure what you're trying to do. The /authorize URL you're constructing is one that the user should browse to, not something you should try to invoke programmatically. It's the page where the user logs in to Dropbox and then clicks the "Allow" button to grant access to your app. Have you tried following the example…

We don't have anything like that built in. We encourage people to use an embedded web browser in their app.

What we usually suggest is to use the WebBrowser control. Why are you trying to avoid that?

Yes, that's right.

In Dropbox, folders are either shared or not. If you create a new folder inside of an already existing shared folder, then that new folder will be shared too. Otherwise it's private to the user.