Take Your Search Game to the Next Level with Dropbox Dash  🚀✨ Curious how it works? Ask us here! 

Forum Discussion

valarmathi's avatar
valarmathi
New member | Level 2
2 months ago

Issue in downloading shared files

I am getting error when i try to download the shared file . 

Error reference :

{ "error_summary": "path/not_found/...", "error": { ".tag": "path", "path": { ".tag": "not_found" } } }

But file is available in my shared file list . At the same time ,i can download file which is available in my own account . This error occurs only when i try to download shared file .Is there any other way to download shared files ? . Kindly update on this issue .

1 Reply

  • DB-Des's avatar
    DB-Des
    Icon for Dropbox Engineer rankDropbox Engineer

    Hi valarmathi

    A "path/not_found" Dropbox API error indicates that the API call failed because there was nothing currently found at the specified path in the connected account under the relevant root. For example, this can happen if there's a mistake or typo in the path value the app supplies, if the file/folder has been renamed, moved, or deleted from that path, if the app is not connected to the correct account for that particular path, etc.

    When specifying the path, make sure you provide the full and accurate path for the desired file under the relevant root. For example, if you have a file named "example.csv" inside a folder named "folder", the path would be "/folder/example.csv". You can find more information on path formats here.

    Here are several things you can check in particular to debug this:

    • Make sure you're using a currently accurate path value: You can use /2/files/list_folder and /2/files/list_folder/continue to list the contents of a folder so you can check what the correct path values would be for items in those folder(s). To list the root, set path to the empty string "" when calling /2/files/list_folder. You can use the path_lower or id values returned for the files/folders in that folder to interact with those files/folders.
    • Make sure you're connected to the correct account for the path value you're using: You can use /2/users/get_current_account to check which account the app is connected to.