Comments
-
Are you referring to the Dropbox desktop client, or an app you made that uses the Dropbox API? If it's the later, what SDK/library are you using?
-
That's a security feature of CORS. I'm not familiar with the dbox library you're using, but you need to make sure you don't use credentials (i.e., the withCredentials XHR field, for example, to set cookies) when making these API calls.
-
To use the Core API, you'll need to register a "Dropbox API app", not a "Drop-ins app": https://www.dropbox.com/developers/apps/create Drop-ins don't have app secrets, unlike Dropbox API apps. And yes, to use the Core API, you'll need to have the user authorize the app to access their account. Then, you can make API calls…
-
You can upload data to Dropbox using the /files_put endpoint on the Core API: https://www.dropbox.com/developers/core/docs#files_put That endpoint accepts both PUT and POST. You can use the HTTP endpoints, such as the above, directly, but we recommend using an official SDK if possible:…
-
The iOS Core SDK is just a wrapper that provides functions for accessing the Dropbox Core API. If you need to run tasks in the background, you can do so in your app, and utilize the SDK to make the API calls. (The official Dropbox for iOS app does use the SDK and implements background functionality as necessary like this.)
-
The iOS Core SDK itself doesn't handle running in the background, so you'll need to implement that in your app if you need it. You'll want to refer to Apple's iOS documentation for managing background tasks:…
-
Yes, you can add the source directly (it's included in the download) and make whatever changes you need.
-
Are you using the iOS Core SDK? This field isn't currently implemented in that unfortunately, but I'll be sure to pass this along as a request. Note that the iOS Core SDK is open source though, so you can modify it if/as desired.
-
It sounds like you're looking for the modifier field returned by /metadata: https://www.dropbox.com/developers/core/docs#metadata
-
You're getting a NetworkOnMainThreadException, which only isn't specific to Dropbox. In short, you shouldn't make network calls (for example, Dropbox API calls like metadata which call the Dropbox API servers) on the main thread. You can find more information here:…
-
How does it fail? (What's the error/stack?)
-
It looks like you're checking authenticationSuccessful but this only returns true during an actual app authorization flow. However, since you're setting your access token manually, this doesn't apply. You can used isLinked to check if you have an access token set instead:…
-
No, we don't have any sample code for this, since it isn't recommended. What error do you get?
-
The Dropbox API was designed with the intention that each user would link their own Dropbox account, in order to interact with their own files. However, it is technically possible to connect to just one account. The SDKs don't offer explicit support for it and we don't recommend doing so, for various technical and security…
-
By "correct user's auth", I meant that in order to get the extra information such as "path", you need to make that API call using an access token for the user account that owns the link. E.g., see the /metadata/link documentation for in_dropbox and path: "in_dropbox: Returns true if the file or folder is in the…
-
[Edit to clarify] Actually, apologies, this doesn't get returned directly by the Chooser, but this is possible to get now depending on the link type setting you're using with the Chooser. That is, if you use the "preview" link type, you can then pass the link to /metadata/link to get the metadata, including path:…
-
There currently isn't an officially supported way to get the original path from a shared link returned by the Chooser, but I'll be sure to pass this along as a request.
-
Your app keys are accessible from the App Console: https://www.dropbox.com/developers/apps Note that you'll need to be signed in to the account that owns the apps to access them.
-
No, unfortunately the API doesn't currently offer any calls for managing shared folders, so you can't use it to programmatically share folders like that. However, if you'd be interested in potentially participating in a shared folder API beta in the future, please sign up here:…
-
It looks like the /Test folder isn't a shared folder (e.g., looking at the icon, which is folder, but would be folder_user for shared folders). It sounds like you mean you only shared it via a shared link. These are actually two different kinds of sharing that Dropbox offers, and include_membership only applies to the…
-
Can you post a sample request/response so we can take a look? Or, feel free to open an API ticket if you'd prefer to send it privately.
-
Regarding the shared folders, you might mean shared links to folders, which is a slightly different type of sharing. For reference, that corresponds to the /shares endpoint. Also, the API can be used with existing shared folders, it just can't currently be used to share or unshare, or add or remove people from folders. In…
-
I can't offer much help for the DropNet library itself since we didn't make it, so you should refer to the documentation/support for that for information on how you process the app authorization flow in it to get and set the access token. It looks like the documentation is here. Note that the API doesn't offer any calls…
-
The "preview" link type isn't meant for programmatic access, so unfortunately there isn't a good solution here. That being the case, the "direct" link type might work better for you, as it does return file content directly, and responds with the expected errors codes in these cases. They do expire after four hours though.…
-
Sorry, no updates on this.
-
Unfortunately, the Dropbox API doesn't offer a way to automate this, but I'll be sure to pass this along as a request.
-
The script you linked to doesn't use an officially supported interface for interacting with Dropbox, but rather connects directly to some internals of the Dropbox desktop client, which isn't recommended. We don't currently have an official API for interacting with the Dropbox desktop client like this, but I'll be sure to…
-
[Cross-linking for reference: https://stackoverflow.com/questions/28605843/osx-dropbox-sync-api-error-unable-to-verify-link-request ]
-
This certainly sounds like something that one could accomplish using the Dropbox API. (I'm not sure what you mean exactly by "metadata tags" though. Dropbox doesn't offer a way to store arbitrary metadata for files, but if you're just referring to metadata stored in the file itself, or on your server, that would be fine of…
-
Hi Craig, this thread was about something slightly different (i.e., getting metadata for the link without using the API at all), but what you found is correct. The get_shared_link_metadata API endpoint doesn't currently support collection links. We'll consider this a feature request for support for that though.