We Want to Hear From You! What Do You Want to See on the Community? Tell us here!
Forum Discussion
awb
2 years agoHelpful | Level 7
The remote server returned an error: (422) Unprocessable Entity.
I'm trying to list all the file and folders in a Dropbox Teamspace and getting the following error
The remote server returned an error: (422) Unprocessable Entity.
"{"error":{".tag":"invalid_root","invalid_root":{".tag":"team","home_namespace_id":"retracted","home_path":"/retracted Dropbox Team Spaces","root_namespace_id":"retracted"}},"error_summary":"invalid_root/"}"
This all looked to be working as expected until a few weeks ago.
If anyone could help it would be much appreciated
Hello awb ,
Based on the error message "invalid_root", this is occurring as the Dropbox-API-Path-Root header "root_namespace_id" value is incorrect. Please cross check if you are using the correct "root_namespace_id" by executing the 2/users/get_current_account endpoint. You can also test the endpoint using our Dropbox API explorer.Please bear in mind that there is a possibility that your account has been updated to our new team space functionality. For further information on the latest updated team space, please review the following link:
While implementing the Dropbox API with the updated team space, you will need to configure your API calls to operate within the "team space", in order to interact with files/folders in the team space. To do so, you'll need to set the "Dropbox-API-Path-Root" header with your Dropbox API request. For further information, please review the following link:
16 Replies
Replies have been turned off for this discussion
- iNeil2 years ago
Dropbox Community Moderator
Hello awb ,
Based on the error message "invalid_root", this is occurring as the Dropbox-API-Path-Root header "root_namespace_id" value is incorrect. Please cross check if you are using the correct "root_namespace_id" by executing the 2/users/get_current_account endpoint. You can also test the endpoint using our Dropbox API explorer.Please bear in mind that there is a possibility that your account has been updated to our new team space functionality. For further information on the latest updated team space, please review the following link:
While implementing the Dropbox API with the updated team space, you will need to configure your API calls to operate within the "team space", in order to interact with files/folders in the team space. To do so, you'll need to set the "Dropbox-API-Path-Root" header with your Dropbox API request. For further information, please review the following link:
- awb2 years agoHelpful | Level 7
Hi,
Appologies in the delay in getting back to you.
"Please bear in mind that there is a possibility that your account has been updated to our new team space functionality. For further information on the latest updated team space, please review the following link:"
This was orinally created as a Team Space, so assumed nothing has changed.
Have all Dropbox customer been migrated to Team Spaces now?
Thanks
- Greg-DB2 years ago
Dropbox Community Moderator
Teams are being updated to the updated team space, though not all teams have been yet.
- awb2 years agoHelpful | Level 7
Thanks Greg, is the plan to move all of your customers on to this? Or is this still optional?
- Greg-DB2 years ago
Dropbox Community Moderator
Dropbox is planning to migrate all teams to the updated team space configuration.
- awb2 years agoHelpful | Level 7
Greg-DB Just wanted quickly followup on something. When you migrate teams to the new team space configuration.
Do the team folder ids change at all? Just noticed some odd behaviour in something I am working on.
Thanks
- Greg-DB2 years ago
Dropbox Community Moderator
The team folder IDs of existing team folders themselves shouldn't change, though member roots can change. There are different scenarios and variables though, e.g., a team migrating from no team space to the updated team space, versus migrating from the team space to the update team space, so please feel free to share the details of any specific issue so we can advise accordingly.
- awb2 years agoHelpful | Level 7
Thanks for the response Greg-DB if I were to list folders in a namespace as an admin and
then as a user. would the folder id be different.
I guess I can test this out when I get a chance.
- awb2 years agoHelpful | Level 7
So I've tested the above.
Ran list folders as member, using the following
dropboxTeamClient.AsMember(account.TeamMemberId).WithPathRoot(new PathRoot.NamespaceId(account.RootInfo.RootNamespaceId))
Each user gives a different id for said Team Folder.
- Greg-DB2 years ago
Dropbox Community Moderator
If you're looking inside the same namespace shared across different accounts, the file/folder ID for any given file or folder inside the namespace should be consistent across accounts. Likewise the team_folder_id or shared_folder_id should be the same.
If you're looking at the mount point of any particular namespace such as team folder itself though inside different roots, the "id" (which identifies the place where the namespace is mounted in that root) would be different, while "shared_folder_id" should be the same.
If something isn't working as expected though, please share the rest of the relevant code and the output so I can take a look at what values specifically you're looking at. Thanks!
About Discuss Dropbox Developer & API
Make connections with other developers815 PostsLatest Activity: 12 hours ago
The Dropbox Community team is active from Monday to Friday. We try to respond to you as soon as we can, usually within 2 hours.
If you need more help you can view your support options (expected response time for an email or 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!