You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.

Forum Discussion

awb's avatar
awb
Helpful | Level 7
8 months ago

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:

     

  • iNeil's avatar
    iNeil
    Icon for Dropbox Engineer rankDropbox Engineer

    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:

     

    • awb's avatar
      awb
      Helpful | 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-DB's avatar
        Greg-DB
        Icon for Dropbox Staff rankDropbox Staff

        Teams are being updated to the updated team space, though not all teams have been yet.