OAuth get file request fails with file not found

Does your app have "Full Dropbox" or "App folder" permission?

In the app folder case, the root of your paths refers to the app folder, so /files/auto/Images/thankyou.jpg will look for a file in /Dropbox/Apps/<your app name>/Images/thankyou.jpg.

It might help if you make a metadata call so you can see what's actually in Dropbox first: https://api.dropbox.com/1/metadata/auto (with the Authorization header). The paths you see there should work when you call /files.

Great. You were spot on. I had placed the files under the root folder and not inside the app folder. It worked after I place my files under the App folder and try making the /files api call.

I had initially tried the metadata api call but it seems that the documentation (https://www.dropbox.com/developers/core/docs#metadata) mentions that the api calls requires the path and I misinterpreted it. Not passing the path works is what didn't click me earlier.

Thanks a ton!

Have the same issue. I have "Full Dropbox" permission

{"error": "File not found"}

Under root I have "folder" folder and inside it left.png 

Path is retrieved by metadata

https://api-content.dropbox.com/1/files/auto/dropbox/folder/left.jpg?oauth_consumer_key=23ji9ydhhprk1tv&oauth_nonce=3b22dde5b2b300000&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1472210676&oauth_token=wy0vvhrabjdh714m&oauth_version=1.0&oauth_signature=nHJ0NC3c6EHocEQVKKJth%2FupO%2Bo%3D

With App folder all works. But I need "Full Dropbox" permission

InF B, /1/files/auto/dropbox/folder/left.jpg looks wrong. Based on your description of the location of the file, shouldn't that be /1/files/auto/folder/left.jpg (no "/dropbox")?

Steve, without "/dropbox" I get 

{"error": "Unauthorized"}

Did you construct the right OAuth signature after changing the URL? (This error sounds like a bad OAuth signature.)

Also, is there a reason you're using OAuth 1 and HMAC signatures? OAuth 1 with PLAINTEXT signatures is easier to work with, and OAuth 2 is even easier.

Also, API v1 has been deprecated, so you may just want to move to API v2 now (which only supports OAuth 2).