Dropbox Extensions are now open to all developers! It's a feature that can be added to your new or existing apps with Full Dropbox access, and is compatible with Dropbox API v2 and OAuth 2.0 flow. You can read more about Extensions in our developer blog or the Extensions Guide.
We'd love to hear how you're thinking about leveraging Extensions, or any other features you'd like to see in Extensions. Please post your comments and questions below and we look forward to hearing from you :).
@umalik-pd Thanks for the feedback! In this scenario, it sounds like the "ROOT/" you're referring to is a Business "team space". Apps with Full Dropbox access can actually access files in the team space that the connected user has access to (for which they may have triggered the extensions flow). API calls do default to the user's own member folder as the root though, as you found, so you'd need to configure your API calls when you need to access the team space instead. If you try to access something in the team space without setting the root accordingly, the call will fail. You can find information on how to configure this in the Namespace Guide.
I'll send this along to the team though as a request to include some way of indicating which root is relevant in the extensions flow.
@umalik-pd I'm not sure I understand your comment. You can lookup and access files passed along the extensions flow from a ("personal" or "user-linked") Dropbox API app with Full Dropbox access, even if the file happens to be in the team space. If the file happens to be in the team space, you just need to set the 'Dropbox-API-Path-Root' header accordingly, as covered in the namespace Guide.