Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
https://api.dropboxapi.com/2/files/list_folder giving response
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:
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.
path
value you're using: You can use /2/users/get_current_account to check which account the app is connected to.
"/Apps/<app folder name>/folder/example.csv"
, you should only send the path
value as "/folder/example.csv"
.
A 'missing_scope' error indicates that while the app is permitted to use that scope, the particular access token you're using to make the API call does not have that scope granted. Also, be aware that just adding a scope to your app via the App Console does not retroactively grant that scope to existing access tokens or refresh tokens. That being the case, to make any API calls that require that scope, you'll need to re-authorize the app to get a new access token (and refresh token, if being used) with that scope. Refer to the OAuth Guide and authorization documentation for more information.
Note that the root_namespace_id returned by /2/users/get_current_account can change in some cases, so it's always best to retrieve the current value when needed.
A no_permission
error can indicate that the account for the access token does not have permission to access to that particular namespace. You can find more information in the Path Root Header Modes documentation here. Note that permissions can change over time, e.g., due to team or sharing setting changes. As a best practice, apps should be written to programmatically catch and handle errors like this, in order to manage these changes. If there's been a change to your team and/or permissions, you may need to check your configuration and update the namespace ID you're using accordingly to perform the calls needed for your use case.
For more information on interacting with team content via the API, please refer to the Team Files Guide as well as this post for information on how to handle the updated team space configuration.
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:
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.
path
value you're using: You can use /2/users/get_current_account to check which account the app is connected to.
"/Apps/<app folder name>/folder/example.csv"
, you should only send the path
value as "/folder/example.csv"
.
A 'missing_scope' error indicates that while the app is permitted to use that scope, the particular access token you're using to make the API call does not have that scope granted. Also, be aware that just adding a scope to your app via the App Console does not retroactively grant that scope to existing access tokens or refresh tokens. That being the case, to make any API calls that require that scope, you'll need to re-authorize the app to get a new access token (and refresh token, if being used) with that scope. Refer to the OAuth Guide and authorization documentation for more information.
Note that the root_namespace_id returned by /2/users/get_current_account can change in some cases, so it's always best to retrieve the current value when needed.
A no_permission
error can indicate that the account for the access token does not have permission to access to that particular namespace. You can find more information in the Path Root Header Modes documentation here. Note that permissions can change over time, e.g., due to team or sharing setting changes. As a best practice, apps should be written to programmatically catch and handle errors like this, in order to manage these changes. If there's been a change to your team and/or permissions, you may need to check your configuration and update the namespace ID you're using accordingly to perform the calls needed for your use case.
For more information on interacting with team content via the API, please refer to the Team Files Guide as well as this post for information on how to handle the updated team space configuration.
I have tried your API to check which account the app is connected to https://api.dropboxapi.com/2/users/get_account and there is response
To check which account the app is connected to, you should use /2/users/get_current_account (not /2/users/get_account).
In my case Dropbox app was created under my email account and admin changed my access from 'admin' to 'member', so software suddenly started giving me 'no permissions' error even when app had all scopes.
A "no_permission" error isn't a scope error. A "no_permission" error would be more related to your file/folder permissions instead.
To clarify, do you still require help with this error? If so, please share:
Hi there!
If you need more help you can view your support options (expected response time for a ticket is 24 hours), or contact us on X or Facebook.
For more info on available support options for your Dropbox plan, see this article.
If you found the answer to your question in this Community thread, please 'like' the post to say thanks and to let us know it was useful!