Not sure how to interpret /users/get_space_usage output for team account

Thanks for getting back to me.

Well, I guess my code is too long to fit into a forum post, but I have already outlined the essence of it.

I have my own app that connects to the Dropbox API (REST HTTP) on behalf of a user to build a breakdown of the user's usage of Dropbox space quota, by scanning all files and folders, calculating their total size, and building a sorted list.

The user in question is a regular user, not an admin / team owner.

On one hand, I query get_space_usage and obtain the overall used space for the team and for this particular user.

On the other hand, I send a sequence of list_folder requests to scan ALL files and folders and calculate their total size. For these requests, I include the Dropbox-API-Path-Root, including the "root" parameter equal to the "root_namespace_id" obtained from the previous get_current_account request. I'm sure the Dropbox-API-Path-Root is working, because after including it, I can see additional shared folders that weren't visible without the header.

However, even with the shared folders included, the outcome is that the total of all files and folders is significantly (order of magnitude) less than the user's own used space reported by get_space_usage.

My question is, how is it possible to explain this striking discrepancy, what are the possible scenarios? What could be using the rest of the used space? Why am I not able to scan it with list_folder?