Steve M. Dropboxer

So far, the only SDK we've released (in preview) for API v2 is actually one for iOS (written in Swift): https://blogs.dropbox.com/developers/2015/05/try-out-swiftydropbox-the-new-swift-sdk-for-dropbox-api-v2/.

Not really. As new SDKs for API v2 come along, we'll probably be writing some more blog posts about how to use them to do common syncing tasks (like listening for changes). For now, I'd wait and watch the blog as the new API v2 develops.

"Is it even possible to sync with the CoreAPI or is it really just a way of uploading and downloading files while the user waits?" I'm not entirely sure what you mean. Syncing generally means uploading and downloading files as well as getting notifications when files change. The Core API does all of these things (and is in…

Using the https://www.dropbox.com/developers/core is the recommended approach. There are existing iOS and .NET (third-party) libraries, and we will be building new ones for API v2 over the coming months. A preview of our Swift SDK just went out yesterday:…

I'm not familiar with the term "access key," but if you're asking about an "access token," that's a term associated with OAuth 2, while the URL you have is dealing with OAuth 1. In OAuth 1, you get an token (oauth_token) and a token secret (oauth_token_secret). If you need to convert that to an OAuth 2 access token, you…

What object reference is not set to an instance of an object? Also, cross-referencing your post on Stack Overflow: http://stackoverflow.com/questions/30366944/how-to-get-access-token-from-dropbox-sync-datastore-xamarin-component.

When you say "dropnet," are you referring to the .NET library (https://github.com/DropNet/DropNet)? If you're migrating from the Sync API, take a look at https://blogs.dropbox.com/developers/2015/05/migrating-sync-sdk-access-tokens-to-core-sdk/ for details about how to extract the existing access token.

Cross-linking with Stack Overflow: http://stackoverflow.com/questions/30391222/dropbox-core-api-in-c-xamarin

Oh, sorry. There's no documentation for the protocol used to talk to the Dropbox app on the phone, but you might want to take a look at the source code for the iOS Core SDK to see how it works.

The Dropbox application on Windows Phone doesn't support #1, sorry. We'll consider this a feature request, but for now you'll need to use the native browser on the device or an embedded browser control in your app.

You need to use https://www.dropbox.com/developers/datastore/docs/ios#DBTable.getOrInsertRecord:fields:inserted:error:DBTable.getOrInsertRecord:fields:inserted:error:.

Dropbox doesn't have the equivalent of a "service account." All accounts belong to users. Is there a scenario you have in mind? Once a user has authorized your app once, you can reuse that access token indefinitely, so there's no need to repeat the OAuth flow. (And if you just want an access token for your own account, you…

Oh, sorry! You're right. My only guess is that you're not using an access token from the right app? Double check that the app permission is what you think it is and that you generated a token for the right app.

Yes, it's the access token you got from the app console or by authorizing an actual user (a Dropbox for Business team admin, in this case). To access this endpoint, though, you do need "team auditing" permission. See https://www.dropbox.com/developers/business/docs#log-get-events.

Here's a little sample to help you get going. This code reads all the events for the team via the event log. (It uses the Python requests library.) params = {}while True: response = requests.post('https://api.dropbox.com/1/team/log/get_events', headers={ 'Authorization': 'Bearer %s' % access_token, 'Content-Type':…

Here's an example of non-numeric enums that I quite like: if let authResult = Dropbox.handleRedirectURL(url) { switch authResult { case .Success(let token): print("Success! User is logged into Dropbox with token: \(token)") case .Error(let error, let description): print("Error \(error): \(description)") } }

Thanks for all the detailed feedback! As requested, let me explain some of our thinking. I'm just one person who worked on this, but I'll do my best to explain the thought process. When we first started work on SDKs for API v2, we looked at a few options for how to support iOS developers: * We could write an Objective-C…

As I said, we plan to add support for Objective-C users. I don't have an ETA yet, but once we finish up the Swift SDK and take it out of beta, it's going to be the next thing we work on in the library.

Back-pedaling here a bit, sorry. After further investigation yesterday, it looks to me like making it easy to call SwiftyDropbox from Objective-C is going to be considerably more work than I thought. I don't think Objective-C support will make it into the initial release of the SDK, but it is something we will look…

For those who haven't tried it yet, I just tried and believe that we'll need to expose the Swift classes to Objective-C explicitly by inheriting from NSObject and adding the @objc decorator. (I was able to make some progress just by making the Dropbox class "@objc public class Dropbox : NSObject", but I believe there is…

I'm a bit confused. Did you run into trouble just using the Swift SDK from your Objective-C project? Or is there some other reason you can't (or don't want to) do that?

For API v2, we only have a Swift SDK and currently don't have plans to build an Objective-C SDK. As Greg mentioned, you should be able to just use the Swift SDK from your Objective-C code. For API v1, the iOS SDK is written in Objective-C, and the code can be downloaded…

Cross-linking with Stack Overflow: http://stackoverflow.com/questions/28301956/dropbox-api-requests-performance-issues.

"All the Dropbox file privacy is built up on that identity, so it is not easily guessable according to Dropbox security standards." I'm not sure what identity you're referring to. The identity of a file in Dropbox is its path, and these are often easily guessable. Even an app that knows about my files in Dropbox certainly…

I think you're referring to the feature on dropbox.com that lets a user click an "open" button to open the file on their local computer instead of in the web browser. There's no API to replicate this. You can imagine why, for security purposes, we don't want other web pages to be able to trigger this behavior.

If you end up making more than one call, I'm pretty sure that consumes more resources on the Dropbox side than if you had just requested all 1,000 in the first call.

Daniel, all of your suggestions are good ones. Thanks. As for what you should do now, why wouldn't you just always request 1000 (the max) revisions? Are you trying to speed the process up? Save bandwidth? Something else?

This specific thread is about the Sync API, which is deprecated, so we won't be making changes to it. More generally, /delta (API v1) and /files/list_folder (API v2) behave similarly in that only the last path segment is "correctly" cased (according to the current casing of the file). There are no immediate plans to change…

Per your other thread, you're probably not going to end up using the Saver anyway. :-) If you use the Core API to upload the file, you can easily upload whatever content you want directly.

The Saver lets a user save a file to their Dropbox, so it saves to whatever account the user is logged in as. It sounds like you always want to upload to a single Dropbox account (yours), no matter what user is visiting your website. If that's the case, you'll need to send the file to your own server and from there write…