Greg-DB Dropbox Community Moderator

The standard way to download a file via the Dropbox API is the /2/files/download endpoint. That returns the file data directly in the response body. If you do need a URL that you can use to download the file, you can call /2/files/get_temporary_link. That will return a link that you can use to access the file data later…

Is that the full error/output? If there's any other error/output, please share that for reference. You may also be able to enable more verbose output by using curl's "-v" option. From what you shared here though, I see you're getting "Address unavailable", which may indicate a DNS issue. The 'api.dropboxapi.com' domain is…

Have you checked the suggestions in my last message?

Any endpoint using "User Authentication" (or "Team Authentication") does require an access token. That includes both the download and the "upload session" endpoints, for uploading large files. The access token can be either a legacy long-lived access token, or a short-lived access token. So, if you're using a short-lived…

The team is reporting that this issue is now fixed and should be working properly. Apologies for any inconvenience this may have caused, and thanks again for bringing this to our attention.

If everything in the connected account accessible to the app is public anyway, that would allay concerns about data leakage at least. There may still be issues with exposing the ability to perform other API calls, such as uploading files, but that could be minimized by restricting the refresh token (and consequently the…

The Dropbox API does offer the ability to programmatically generate file requests, via the /2/file_requests/create endpoint. This isn't restricted to any particular platform(s). You can make Dropbox API calls anywhere you can perform HTTPS requests. I can't offer guidance for Woocommerce/Wordpress/Trello in particular…

I recommend trying out the Embedder to see if it works for your use case. That would be the safest way to do this. That works by supplying it a shared link to the folder you want to display. Otherwise, you would need to use the API, which would require a refresh token for this scenario. Like the now-deprecated long-lived…

This looks like it may indicate an issue with the installation of the Dropbox library in your project. How did you install the Dropbox library, and what output did you get when you did? If something went wrong, it may help to try to uninstall and reinstall it.

I'm not sure understand what you mean what you mean by "temporary code". The authorization flow with authorizeFromControllerV2 works effectively the same as it did with authorizeFromController, since the SDK handles the refresh flow for you. Just like with authorizeFromController, you can just process the authorization…

Even if you've uninstalled the app, the client may still be saved locally since that's persisted in the iOS keychain. And if you've disconnected the app via the Dropbox web site, the SDK won't yet know that the connection has been revoked on the server until you attempt an actual API call, like listFolder, at which point…

That is how you check. You can check if authorizedClient is nil or not. If it is not nil, that means you have a saved client to use for that user. (And if the app was disconnected from the account server-side, attempting to use it will accordingly fail with an error.)

You do not need to send the user through the authorization flow every time they want to use the Dropbox integration. You can have them authorize it once, using authorizeFromControllerV2, and the SDK will automatically store the resulting access token and refresh token for you. You can use authorizedClient to check if you…

Thanks for the additional information. From this I see you're using the 'authorizeFromController' method. You'll need to switch to using the 'authorizeFromControllerV2' method instead as shown here to support the new flow. Once you do so, the SDK will automatically handle short-lived access tokens and refresh tokens for…

The new short-lived access tokens used by the Dropbox API do expire after four hours, at which point you'd get this 'expired_access_token' error. In that case, you would either need to have the user re-authorize the app to get a new short-lived access token, or if the app requested "offline" access, use the refresh token…

No, unfortunately the Dropbox SDKs don't officially support React Native.

It sounds like you're describing the app authorization flow built in to the official Dropbox mobile SDKs. You can find those here: * for Swift on iOS: https://github.com/dropbox/SwiftyDropbox * for Objective-C on iOS: https://github.com/dropbox/dropbox-sdk-obj-c * for Java: https://github.com/dropbox/dropbox-sdk-java (see…

Another update: SwiftyDropbox now supports Alamofire 5 as of v8.0.0.

As you found, app folders are incompatible with shared folders, meaning you can't share an app folder, put a shared folder inside an app folder or put an app folder in a shared folder. Instead, if you need to use the API with shared folders, you'll need to use "full Dropbox" permission, as opposed to the app folder…

Yes, that's correct. Technically the short-lived access token isn't needed there, since the SDK will automatically use the refresh token to get a new short-lived access token whenever needed.

Thanks! In this latest screenshot I see you're now getting the error "shared_link_already_exists". That means the "shared link already exists" for the specified item, so you can't create another for that item. I see it's also indicating that it's returning the existing shared link metadata in the error object in this case,…

Hubo un error con este método en versiones recientes de .NET SDK, pero lo solucionamos en la última versión. Si aún no está usando v6.11.1 del .NET SDK, actualice a eso e intente nuevamente. -----------– Disculpa la calidad de la traducción. Hemos utilizado un traductor en línea para crear las respuestas. Nos gustaría…

No, I don't have an update on this feature request.

The "don't have any API limits at all" claim you quoted was not posted by a Dropbox employee and is not accurate. 1. The Dropbox API does have a general rate limiting system that applies to all account types, including free accounts, but we don't have any specific numbers documented for that. It is relatively generous…

From a technical perspective, it should certainly be possible to use the same access token in multiple places like this. So, to help narrow this down, can you confirm it's the 'filesUpload' call in particular that doesn't complete? Does the 'filesListFolder' call work or not? Since the code is running in each individual…

The Dropbox API does not offer functionality for controlling the desktop client like that, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. You may want to consider instead using the Dropbox API to upload the file, which is done by communicating directly with the…

No, there's nothing quite like that. Beyond accessing the contents of a shared link directly, you'll need to use the API as documented, e.g., by passing up an OAuth 2 access token.

As long as the refresh token is valid, it's not necessary to update the credentials. The SDK will automatically perform a refresh using the existing refresh token whenever needed.

The Dropbox API itself does not technically require that these two changes (scopes and SLT/PKCE) be done at the same time. It is possible for a non-scoped app to use SLT/PKCE, and it is possible for a scoped app to not use SLT/PKCE. However the Android authorization flow built in to the Java SDK was updated to handle both…

Yes, when using 'response_type=code', you'll get back an "authorization code", not an "access token". You can exchange the authorization code for an access token by calling /oauth2/token. When using 'response_type=token', you'll get back an access token directly. The 'response_type=token' flow is no longer recommended…