Greg-DB Dropbox Community Moderator

No, unfortunately Dropbox doesn't offer the ability to set/get the API file properties/templates via the official Dropbox user interfaces, such as the desktop client or web site, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. 

The SDK should handle the refresh for you automatically. Can you double check that you have the correct access token, refresh token, app key, and app secret values though? For instance, you need to use the same app key and app secret you used to originally get the refresh token in order to use the refresh token to get a…

@"OFV" When your "DropboxClient is instantiated with the Access_token and refresh token", are you also supplying the app key and secret? Those are required to perform the refresh. Make sure you're doing so, like in the example here.

Even if the folder is empty, the folder itself would have a path, but again it would only be returned if the accounts match. We'll look into it and follow up with you on your ticket.

This behavior sounds unexpected, so please open an API ticket from the account that owns the affected app so we can investigate. Please include: * the name or key of the affected app * the affected webhook URI * a sample timestamp of when this occurred Thanks!

Yes, using sharingGetSharedLinkMetadata is the right way to get the corresponding path just based on the shared link. If that's not working properly for you, please share a sample so we can look into it. For instance, share the output of both usersGetCurrentAccount and sharingGetSharedLinkMetadata, as well as the shared…

Apologies for the confusion. You can start a concurrent upload session in the .NET SDK by passing an empty body, like this: var uploadSessionStartResult = await _client.Files.UploadSessionStartAsync(sessionType: UploadSessionType.Concurrent.Instance, body: new MemoryStream()); I'll ask the team to see if we can update the…

Thanks for writing this up and sharing the context. Unfortunately, no, I don't believe the Dropbox .NET SDK offers a way to retrieve the current short-lived access token like this, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. 

How are you checking that you're using an access token for the same account as the one that made the shared link? I just tried this functionality and it is working for me. When using the same account, I get the path_lower value. You can use the usersGetCurrentAccount method to check what account a particular access token…

Thanks! I was on an older version where it does work in Chrome, for whatever reason. I'll ask the team to look into that variant as well.

Thanks for the post. Unfortunately, that behavior is expected sometimes, and there isn't a way to just prevent it. The original casing isn't always available for all components. There's a note about this in the API v2 documentation, under "Case insensitivity": Also, while Dropbox is case-insensitive, it makes efforts to be…

Thanks for the post. While the Dropbox Chooser for Android isn't officially marked deprecated, it hasn't been updated in several years. I'll send this along as a request to either update that or officially deprecate it.

@"OFV" The Dropbox client in the SDK can and will automatically handle the refresh for you, and you shouldn't even need to access to refresh token or new access token after a refresh. The refresh token doesn't change, and the client will automatically set its new access token. And if you need another client, you can just…

@"ozdev" This is open with engineering, but I don't have an update on it yet. I'll follow up here once I do.

This seems to be a duplicate of this thread. Please refer to that for more information.

When you say "the user account that I used is an authenticated user dropbox account.", that doesn't necessarily meet the requirement. In order to receive the path_lower value, the account for the access token you're using to make the call needs to be the same account as the one that created the shared link.

I'll be happy to help with this however I can, but I could use some more information. Can you share: * the HTML/code you're using on your page for the Embedder * what, if any, unexpected error/output you get in the JavaScript console on your page * the URL to a sample page showing the issue Feel free to open a ticket here…

@"phbd" No, unfortunately I don't have an update on this request right now.

The SharingFileLinkMetadata.path_lower (as returned by sharingGetSharedLinkMetadata) is "only be present only if the linked file is in the authenticated user's dropbox.". So, it sounds like the linked file doesn't exist in the account that you're connected to. In that case, you'd need to supply the path yourself. For…

Got it, thanks! This is open with engineering for the case where "Prevent cross-site tracking" affects this. I'll follow up here once I have an update on that. I still can't reproduce the behavior you're seeing in Chrome though. Can you let me know what version of iOS and Chrome you're seeing that with?

Dropbox does offer an API you can use for listing, uploading, and downloading files, among other operations. You can find everything you need to get started with the Dropbox API, including documentation, tutorials, and SDKs here: https://www.dropbox.com/developers For example, to upload a file, you can use:…

Using the official Dropbox API v2 JavaScript SDK, if you want to download a file, you should use the filesDownload method. If you want to download an entire folder, you should use the filesDownloadZip method. If you need a link to a file, you can use the filesGetTemporaryLink method. There isn't an equivalent of that for…

@"liftbox" No, unfortunately I don't have an update on this feature request. This call still only supports specifying one category at a time.

Yes, ideally we'll be able to resolve this on our side, but we just want to make sure we're reproducing exactly the issue you're reporting. So, to be clear, if I understand your messages correctly, the issue does not appear on my sample site for you when you have "Prevent Cross-Site Tracking" disabled, but does still…

If you use the SDK and implement the authorization flow as documented, i.e., using authorizeFromControllerV2, the SDK will actually automatically handle the short-lived access token and refresh token logic for you.

No problem, I'm happy to help. For reference, some account types have the option to set an expiration on shared links, via SharedLinkSettings.expires, but by default there's no expiration.

@"Miros" Modified time is available for files, but not folders. Created time is not available for either. You can find the full documentation on the different pieces of metadata that are available for different types in the documentation, such as for /2/files/get_metadata.

First, for reference, that /1/shares URL is part of API v1, which is retired. If you're using the Python SDK and want non-expiring shared links, you should use sharing_create_shared_link_with_settings. That allows you to programmatically create shared links that don't expire by default (but can be revoked by the user/app)…

Thanks for the additional information. I just tried reproducing this with that code, and it only reproduces for me with "Prevent Cross-Site Tracking" enabled (and works fine with it disabled). Please try this sample I just put up with this code (though I had to add a missing "link"…

Thanks! We'll follow up with you there shortly.