Greg-DB Dropbox Community Moderator

While the initial authorization needs manual user intervention to authorize the app, the user does not need to be present after that. If your app requires long-term access without the user present, you should request "offline" or "background" access via the OAuth app authorization flow. That way, you can get a refresh…

Thanks for the report! This is a bug on our side. We're looking into it. I'll follow up here once I have an update on that. No action is required on your part.

When uploading to a "/apitul" link like this, the file data to upload needs to be sent in the HTTPS request body as "application/octet-stream". Exactly how you do that will depend on your scenario and the client you're using (curl, in this case). For example, with curl, you can use curl's "--data-binary" parameter to…

Normally, you should implement the OAuth app authorization flow in your app, as shown in this example, in order to allow the end-user to connect their own Dropbox account so the app can receive the access token for that user's account programmatically once they approve it. If you are only connecting your own account in…

Since you can't look up which file request was the source of any particular new file directly, using a distinct folder per file request is a good solution. And you can monitor all folders for changes, and see which folder(s) had changes. I reccomend reading through the guides I linked to first for reference. If you want to…

The 'missing_scope' error indicates that while the app is permitted to use that scope, the particular access token you're using to make the API call does not have that scope granted. Be aware that just adding a scope to your app via the App Console does not retroactively grant that scope to existing access tokens. That…

When using files_list_folder_continue, the cursor you pass in should be the last cursor returned by files_list_folder or files_list_folder_continue. You seem to be correctly saving that cursor via 'cursor = entries.cursor', however you overwrite it via 'cursor = cnxn.cursor()'. I don't see where 'cnxn' is defined, but…

Previously, Dropbox API access tokens did not expire, but we have begun moving to a new model of using short-lived access tokens with refresh tokens. You can find more information here. If you do need long-term access, you should migrate to using "refresh tokens", by requesting "offline" access. Make sure you're using the…

The Dropbox API doesn't offer a way to monitor and retrieve information about uploads to file requests in particular, but I'll pass this along as a feature request. You can monitor for changes to any arbitrary path though, such as the folder where uploads for a file request are sent. I recommend reading the File Access…

The current version of the .NET SDK is not currently strongly-named, but I'll raise this with the team to ask them to implement that.

In order to make API calls, you will need to have an API app. The 'missing_scope' error indicates that while the app is permitted to use that scope, the particular access token you're using to make the API call does not have that scope granted. Also, be aware that just adding a scope to your app via the App Console does…

The Dropbox API does not support the "client_credential" grant type, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. 

I can't make any guarantees on the implementation of the Dropbox API servers, but yes, I expect this is about what is happening. 

It sounds like you may be interested in the Dropbox "file request" feature, which is a way to get a link to a page where people can upload files to a pre-specified folder in your account. You can also create file requests programmatically, via the /2/file_requests/create endpoint (or corresponding native method in an SDK).

I see, thanks, that's helpful. Yes, it looks like this is because this "JabpSync" app hasn't been migrated to use scopes yet, but this startOAuth2PKCE method does set scopes. Apologies for the generic error message though. I'll ask the team if we can get a better error returned in that case. Anyway, to address this, you…

No, we don't have a way to get refresh tokens for existing long-lived access tokens. However, while long-lived access tokens are now considered deprecated, but we don't currently have a plan to disable existing long-lived access tokens. (If that changes, we will of course announce that ahead of time.) That being the case,…

That particular error message doesn't sound expected. Can you share a screenshot? Also, if that's occurring in the browser, please share the URL of the page that's failing. Or, if that's occurring in the official Dropbox Android app, please share the version of the the official Dropbox Android app you have installed.…

Thanks for writing this up! I don't believe this anything to be concerned about. It looks like this is just the result of some implementation details on our side. (For example, it seems like the client_modified is taken from the time of request, if not explicitly set, whereas server_modified is when the file is committed…

If you want to manually browse the contents of your own Dropbox account, you can do so using the standard Dropbox products, such as the Dropbox web site at https://www.dropbox.com/home . To list the contents of the connected account in your own app, you can use the listFolder and listFolderContinue methods. And to download…

@"eranga119" This error message indicates that instead of just sending the expected "application/json" value in your "Content-Type" header, you're instead sending that plus the JSON string for the API call parameters, as Здравко said. That JSON should be sent in the request body, not a header. The code you shared does seem…

Long-lived access tokens are now considered deprecated, but we don't currently have a plan to disable existing long-lived access tokens. (If that changes, we will of course announce that ahead of time.) That being the case, your users can continue using their existing long-lived access token(s). And yes, you can test your…

We can't provide support for S3 itself, but if you can get a link to a file on S3, you could then pass that link to /2/files/save_url to save the linked file to Dropbox, without downloading it locally. That's available as files_save_url in the official Dropbox API v2 Python SDK. That can be used by any kind of Dropbox…

A 'path/conflict/folder' error like this indicates "There’s a folder in the way". That is, the folder could not be created because there's already a folder at the specified path. 

It looks like there are a few things here, so I'll try to address them each: First, note that you don't need to register a redirect URI of "https://db-ht5jlmr230u0823" on the Dropbox web site. The SDK and API will handle that for you. You just need to register your URL scheme of "db-ht5jlmr230u0823" as instructed. The…

Thanks for the feedback! I can't speak to why any particular feature was or wasn't implemented, but we appreciate you taking the time to share this. I'll send it along. If you have a shared link for a folder and wish to get a direct link to that, you can likewise modify that as documented here. For folders, that will give…

Right, whenever possible, it's best to avoid unnecessarily uploading/downloading locally, for the sake of reliability and efficiency. Passing a link between two services, if supported, would likely be faster. In this case, if you need a direct link to a file hosted on Dropbox, the specifics will depend on if the file…

This "Your app is not permitted to access this endpoint" error indicates that the access token you're using to make the call does not have the necessary scope needed for calling that particular endpoint. As indicated by the error message in this case, the app would need the "files.metadata.read" scope. You can add it via…

If you want to run the SDK tests, you'll need to plug in the relevant values here. (Running the SDK tests isn't strictly necessary for using the SDK in your own app though.)

It sounds like you're using the Dropbox API v2 Objective-C SDK. That implements the app authorization flow redirect by using a custom URL scheme that you need to register for your app. In your case, based on the output here, your URL scheme would be "db-03609z0wg843bb3". Make sure you've registered that in your app's…

That example and the SDK are not limited to only your own account. That example implements the OAuth app authorization flow, to get an access token for the end-user, whoever that may be. I recommend reading the OAuth Guide for an overview of how that works.