Greg-DB Dropbox Community Moderator

Based on the error message you posted, this is failing because your machine was unable to look up the 'content.dropboxapi.com' host. That's the correct hostname, and it is resolving correctly for me. That being the case it appears to be an issue with your DNS server, which is out of our control. Please check on your DNS…

There isn't a way to check the progress of an in-process upload remotely via the API. Depending on what, if any, SDK or library you're using though, there may be a local progress callback available though. (For example, here's a sample of using that in the Objective-C SDK.) Check the documentation for whatever SDK/library,…

If you're getting a 413, it indicates that you're passing too much data per request. For each of these three endpoints, you shouldn't pass more than 150 MB per request, per the documentation: https://www.dropbox.com/developers/documentation/http/documentation#files-upload_session-start…

I don't have a sample implementation for using upload sessions in PHP unfortunately. Can you print out the full HTTP response body you're getting? It should contain a more detailed error message indicating the issue. If you still need help, please also share the code you have so far so I can take a look, in addition to the…

I don't have an update on this unfortunately.

I just double checked this, and again there doesn't seem to have been an issue here. It's important to keep in mind that users/shared folder owners can move around content, and change permissions, at any point in time. It's also possible for any particular user to not actually be a member of a team folder (or of a group…

Thanks for the report! There shouldn't be a delay for getting file metadata like this after a file is uploaded. I just looked into this, and as far as I can tell, that error was correct at that time. I can't disclose private account information of course, but it is possible for users to gain/lose access to files or folders…

I'm closing this thread in favor of the duplicate: https://www.dropboxforum.com/t5/API-support/API-V2-Upload-Limit/m-p/272062#M16150

It sounds like you're using /2/files/upload. That endpoint does have a file size limit of 150 MB. For larger files, you should use upload sessions instead. This works the same way for both paid and free accounts.

No, it's not possible to set arbitrary expirations on those temporary links, but I'll pass this along as a feature request. Note that you can modify the shared links from sharing_create_shared_link_with_settings for different behaviors if that helps: https://www.dropbox.com/help/desktop-web/force-download

I can't offer help with lua itself, but it looks like you may not have it configured to actually use https and so it's falling back to http. Dropbox API calls requires https though, so it is redirecting you to https. It looks like there's more information about configuring https support in lua here:…

It sounds like you're using code written for an older version of the SDK with a newer version of the SDK, where the method definition has since been changed. You can find the documentation for the current method definition here. You can also have Xcode fill this in automatically using the Xcode autocomplete feature. E.g.,…

No, unfortunately I don't have an update on this. You'll need to use /2/files/restore (or a corresponding native method in an SDK/library) to restore individual files as desired.

No, I'm afraid I can't share any internal information. Apologies I can't be of more use! I'll be sure to reply here if/when I have any useful information to share.

We've had our engineers working on this and the good news is the problem has been fixed. Please try again and you should find that this functionality works correctly.

For the issue listing the namespace by namespace ID, please share some sample code and full output so I can take a look. Yes, if you register a Dropbox Business API app for team member file access notifications, you will get notified for changes to any member account. From the documentation: "Note that a single change to a…

Based on the internal information available to me (the code, etc.), it appears it will not be a trivial fix.

The Dropbox API doesn't offer a faster way to create shared links, e.g., a batch call for this, but I'll pass this along as a feature request.

As a security feature, OAuth 2 redirect URIs must be pre-registered exactly. Variables/wildcards are not supported in Dropbox OAuth 2 redirect URIs. What you can do instead is encode the necessary information in the 'state' parameter, and decode it as necessary after the redirect back to your app, to handle it as…

To clarify, there isn't an option for you to recover it from the App Console, but if necessary we can manually recover it for you. You can open an API ticket to request that if so: https://www.dropbox.com/developers/contact Anyway, no, if you register a new app with the same name, old access tokens for the old app will not…

My understanding is that it is not in fact a particularly simple change. In any case, I'm afraid I don't have any news on this. Apologies I can't be more helpful!

No, if your app was in "development" mode, there isn't an option for restoring it after you delete it. When you delete an app in development mode though, it frees up the name, so you can register a new app using the same name: https://www.dropbox.com/developers/apps/create

The official Dropbox API v2 .NET/C# SDK doesn't officially support Xamarin/iOS unfortunately, so it doesn't implement the app authorization flow where the official Dropbox iOS app is used (via dbapi-2). Further, that flow where the official Dropbox iOS app is used is only meant for use by the official Dropbox iOS SDKs…

I'm afraid I don't have any details or a potential timeline to share. This issue is open with the team, but I don't have any feedback on it.

If you have a Dropbox Business API app with the "team member file access" permission, using /2/files/list_folder with the Dropbox-API-Select-User header and path="" and recursive=true is the right way to list the all of the contents of a user's account. You can also specify a namespace in the path value instead. Check out…

This is the expected behavior, and it is unlikely to change. I'll be happy to pass this along as feedback to the team though. Can you elaborate on how this causes issues for your app? You can check that the folder has been shared via the `sharing_info` included in the new folder metadata, in order to reconcile the deletion…

The API v2 Java SDK for Android doesn't offer automatic offline support like the Sync SDK did, but I'll be sure to pass this along as a feature request. That being the case, if you need offline support, you'll need to implement that in your app's logic. Apologies I don't have better news!

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

I'll make a note to follow up on this thread if/when this feature is implemented and released.

The Dropbox API is a server-side API insofar as the API calls are made to the Dropbox API servers, which process the requested calls on the server. Your other question seems to be a duplicate of your other thread: https://www.dropboxforum.com/t5/API-support/How-to-append-to-existing-file/m-p/271603#M16083