My company has several applications that interact with the Dropbox API via the python sdk. At some point in the last few weeks, these applications have stopped being able to download files. Neither the application nor the wrapper library that operates the Dropbox python library have changed.
For example, one of our applications attempts to access the following path (obfuscated for security):
/Application Data/app1/big csv file.csv
This worked until recently but now fails due to a path not found error. I'm able to replicate this with test files in shares that have no spaces in the path, just to rule that out. This also fails, both using our library and by calling the API directly with curl:
$ curl --location
--request POST 'https://content.dropboxapi.com/2/files/download'
--header 'Dropbox-API-Arg: {"path":"/Development/testfile.txt"}'
--header 'Authorization: Bearer <redacted>'
{"error_summary": "path/not_found/..", "error": {".tag": "path", "path": {".tag": "not_found"}}}
I tried generating a new access token for the Dropbox-side scoped application. No Joy. I made sure that app has the right scope permissions, it does.
Has something changed in the past two weeks that would require a change on our side? Am I missing something?