Child Item

API Error "path/not_found" when creating shared_link

When interacting with the API, I get a path/not_found error. This happens when I upload a file to dropbox using the path /2/files/upload. After that, I create a link to the file using the path /2/sharing/create_shared_link and specify the path_display received after uploading the file. The error occurs very rarely, but it does not allow you to get a link. What could be the problem?

Find more posts tagged with

API

Shared Links

Upload

Abuse

Promoted

Comments

Greg-DB

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. I notice you mentioned you're using the path_display value, but that's only meant for displaying the value back to the user, not for making other calls. For performing other calls, use path_lower instead for the correct path value.
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.
Make sure you're using app folder-relative paths, if your app is registered for the "app folder" access type: Apps with the "app folder" access type can only access the contents of the special app folder that gets automatically created for it. If your app has the "app folder" access type, then it will only be able to access files in the app folder, and the root for any path value supplied by that app will automatically be the app folder root. You can find more information on app permissions here. For example, If your app has the app folder access type and you're trying to access something you can see on the Dropbox web site at "/Apps/<app folder name>/folder/example.csv", you should only send the path value as "/folder/example.csv". Alternatively, if your app is registered for the "app folder" access type but you need to access contents outside the app folder, you'll need to use a different app registration with the full Dropbox access type instead.
Make sure you're accessing the relevant root: When using an app with the "full Dropbox" access type, API calls default to the member folder, but if you're trying to access the "team space" (only applicable to members of a team with the "team space" configuration), you'll need to configure that as the root explicitly, as covered in the Team Files Guide.

Nick K

I use the PathDisplay that returned from Dropbox API request (/2/files/upload). And when i try to create shared link error is reproduced randomly. The first request may return an error, and the second identical one may succeed. For example, on the third attempt it turns out to upload a file and get a link (the code does not change). I use App Folder access

Greg-DB

Thanks for following up. I'll be happy to help with this issue, but I'll need some more information. Please reply with:

the name and version number of the platform and SDK/library you are using, if any
the steps to reproduce the issue, including relevant code snippet(s), but don't include any access or refresh token(s)
the full text of any error or unexpected output