You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Forum Discussion
Dropbox Error 401: Unauthorized API Call
Hello, guys. I'm having unexpected issues trying to download all the files in a folder from Dropbox using the "https://content.dropboxapi.com/2/files/download_zip" API Call Request. But, I keep recei...
Are you using an app registered for the "app folder" access type? If so, it would only have access to contents of the special app folder that gets created for it. The folder in your screenshot isn't an an app folder though, so you'd need to use an app with the "full Dropbox" access type to access that. You can't switch the access type on an existing app, so you'd need to register another one here and switch to using token(s) for that one.
Alternatively, you can move that folder into the app folder, as long as it isn't a shared folder. (App folders can't contain shared folders.)
Here you have a SS from Postman
Greg-DB
Dropbox Staff
Dropbox StaffFrom the configuration in the UI in your screenshot, it looks like your client may be trying to parse the response as JSON, but the response isn't guaranteed to be JSON, so please check the raw response.
If the raw response is empty though, please check and share the headers as they may help indicate the issue. In that case, please ideally share both the request and response headers, but be sure to redact any sensitive values, such as the access token.
In any case though, it also appears you're trying to send your path parameter as a header named "path", however the parameters for the /2/files/download_zip call should be sent as JSON in a header named "Dropbox-API-Arg". Please refer to the documentation for the /2/files/download_zip endpoints for information on how to correctly format the request. The API v2 Explorer can also be helpful for prototyping and testing out calls.
These are the headers:
The authorization token starts with: sl.B_cyu, does it work for you?
- Greg-DB
Thanks for following up with the additional information.
That looks like the right start of an access token. Looking at your headers though, your "Dropbox-API-Arg" value looks to be formatted incorrectly. Specifically, both:
- it has extra slashes, which are normally meant for escaping slashes in the command prompt but aren't needed in Postman
- the accented character needs to be encoded in the header (which Postman apparently doesn't do automatically). Refer to the documentation here for information on how to encode these values in headers.
So, for example, your Dropbox-API-Arg value would be:
{"path":"/Automatizaci\u00f3n Inteligente/CSV"}Thanks, it worked! But now the path seems to be incorrect since I'm receiving the error 409 conflict: "path/not_found/.."
But, that's the directory in my Dropbox.Maybe I'm missing something?
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
