Greg-DB Dropbox Community Moderator

@"terryz" I see you're setting the "url" to "https://www.dropbox.com" now, instead of your shared link, and so you're retrieving the HTML of the Dropbox home page. I also see that you're trying to set a "Path" header to "/s/y5jlwu5nfr3s8xe/FAULTMSG.CSV?dl=1", however that should be part of the HTTP start line, not a…

That error is occurring because you're missing the "new" necessary to create that instance. Please add the "new" back like in my message and try again.

For the update write mode, you need to supply the rev value that you are intending to update, so you would make that like: new WriteMode.Update(result.Rev)

Please use Dropbox.Api.Files.WriteMode.Overwrite.Instance to set the overwrite mode (instead of AsOverwrite).

@"mdiazl" You should be able to download a file in the connected account using the files_download_to_file method. That should work for files in shared folders as well, as long as the shared folder is mounted in the connected account. Alternatively, if you want to download a file from a shared link, you would instead use…

@"ram4444" As Здравко said, your output may not actually be representative of the real request. I tried replicating the request in curl using the header values you supplied, but the call succeeded for me. That may indicate that the output in fact does not sufficiently show what the actual request consists of. That being…

@"ram4444" I understand you're including the parameters on the URL itself, but the actual HTTP request issued by your client would involve some start line and header(s) at least. So that we can investigate the request that causes that error, please print out and share the actual HTTP request itself. You may need to refer…

@"ram4444" Can you share the full HTTP request (headers and body, if any) that results in a 503 so we can look into it? Be sure to redact your refresh token, app key, and app secret values though. Please also share the full response (headers and body, if any) for reference. Thanks in advance!

Dropbox does not limit how many apps you can register, however Dropbox also does not support registering apps programmatically. You should only be registering apps manually. You should create one app registration per actual app that you are building. That only needs to be done once per app so it should be manageable to do…

If the client is actually sending that full URL string in the start line, that would be incorrect. The start line in the HTTP request should only contain the method, path, and HTTP version; not the hostname/port. And the "Host" header should only contain the hostname. For example, see that part of the first request in your…

@"terryz" No, the values there appear to be valid, and nothing seems to be missing when compared to a curl sample. The only thing that looks off is that the whole URL is output under a description of "requestParams.method", but that may just be how the client is formatting its logging; it may not be representative of how…

@"terryz" Given that the same link and headers work in another client, it does sound like your client is malforming the request somehow. Unfortunately we can't offer support for third party clients themselves, so I recommend referring to the documentation/support resources for that client for information on how to debug…

@"terryz" Thanks for clarifying. Yes, that error would indicate something went wrong with the transfer, but it sounds like curl was able to recover and complete the download successfully. It may have just been a transient network issue. Regardless, it doesn't appear to reproduce the original 400 error code from your…

@"terryz" I see you are getting the two expected 302 responses, and then the final successful 200 response. When you say it fails, are you referring to the "schannel: failed to decrypt data, need more data" message? That doesn't occur for me, and I do get the expected 6848 bytes of data saved out when I try. Does the file…

@"Здравко" Thanks for the note. Yes, that would require the use of some server-side component.

@"terryz" You can run the curl example I shared in my earlier comment to see how the requests are formatted. (There are some redirects involved, but curl will handle that automatically since "-L" is specified.)

@"Gcleanwood" The API was designed with the intention that each user would link their own Dropbox account, in order to interact with their own files. As Здравко mentioned, while it is technically possible to always connect to just one account for all users, we do not officially support this, for various technical and…

You can delete an app itself without losing the data in the connected account(s). Deleting an app registration does not delete the corresponding app folder(s) or the data contained within them. It would only prevent further API calls for the app from succeeding. You can also rename or move the app folder or the parent…

@"terryz" The HTTP GET method is correct for this scenario. It's often the default for HTTP clients, so even when you don't specify it, clients will usually use GET automatically.

@"terryz" Thanks for sharing that, though unfortunately I don't think that we'd be able to determine the issue from that; a 400 like this should generally indicate that there was something incorrect about the HTTP request, but the request data would be encrypted in that capture so we couldn't read it anyway. Perhaps…

@"Goldmine" Using the options.path parameter on /2/files/search_v2 is the right way to restrict the search to a particular folder. (By the way, the API v2 Explorer can be useful for trying out calls like this.) I just tried that and it is working for me. If that doesn't appear to be working for you, please share the code…

@"magnafire" Thanks for the feedback! I've added your note to the feature request.

Using /2/sharing/get_shared_link_metadata is still the right way to get metadata from a shared link, and that now supports both User Authentication (using an access token, as before) as well as App Authentication (using an app key and secret instead of an access token). If that works better for your use case now, I suggest…

There isn't a specific period you should use when polling a job status like this, but in general just a few seconds would be reasonable, say 1-3 seconds between calls to check. If you know it's a particularly large job and may take longer, you might want to make that a little longer. If any particular job fails, the result…

Thanks for the report. It looks like this occurs when the user's account does not have its email verified. I'll ask the team to fix up that error reporting. You should be able to resolve this by verifying the email address on the account.

One reason for the search results being different across users is if the users have different contents in their accounts, e.g., if the relevant items are not currently mounted in an affected user's account. I see you also open a support ticket for this though, so we'll review this specifically for you and follow up with…

No, the "rev" value, e.g., as returned by /2/files/list_folder[/continue], is an opaque revision identifier. It can be used for a strict equality check with other rev values, but it's not meant to be modified, and shouldn't be used to attempt to determine if a rev is older or newer than another. For information on how to…

This should be fixed now. Please let us know if you're still seeing any issues.

This should be fixed now. Please let us know if you're still seeing any issues.

This should be fixed now. Please let us know if you're still seeing any issues.