Unfortunately, the Dropbox classes are fairly recent and the documentation for them is still in development.

A typical Dropbox session consists of the following steps:

1) Initial authorization:
- set the AppKey and AppSecret properties according to the values you received from Dropbox, then
- call the StartAuthorization() method.
- Get an authorization link by calling the GetAuthorizationURL() method.
- Open the authorization link in a browser and sign in to Dropbox.
- Once the in-browser authorization is completed, call the RequestAccessToken() method. Now you can use the values assigned to AuthTokenSecret and AuthToken properties to authorize to the service.

Note that the session is cached for some time on the server, so you do not need to perform complete in-browser authorization each time you want to access your Dropbox account. In other words, you can cache the values assigned to AuthToken and AuthTokenSecret properties after the initial authorization is completed, and assign them back to the properties whenever you need to access the account.

2) General work: use List, WriteObject, ReadObject and other methods to manage objects in your Dropbox storage.

Thanks, we are trying it out. But is it necessary to get authorization? If it's for treating public folders of a customer, we could just work with a given url I guess, and perform a GetAuthorizationURL() or something?

We use cookies to help provide you with the best possible online experience. By using this site, you agree that we may store and access cookies on your device. You can find out more about and set your own preferences here.