Can't create new folder at root level of Dropbox using API

It seems like Dropbox allows us to use the API to create folders at the root level of our Dropbox directory if we have signed up for one of Dropbox's "individual/personal" plans.

However, as soon as we upgraded to one of Dropbox's "team" plans, we can no longer use the API to create folders at the root level of our Dropbox directory.

In other words, if somebody is on a personal pricing plan with Dropbox, writing to the root directory is allowed via the API. But as soon as someone upgrades to a Teams plan with Dropbox, writing to the root directory via the API is no longer allowed. 

Are there any other solutions to this, besides downgrading back to an individual/personal plan?

Hi RFrendt​ 

By default, API calls to the Dropbox API operate in the "member folder" of the connected account, not the "team space". 
 
You can configure API calls to operate in the "team space" instead though, 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. You can find information on how to use this in the Team Files Guide.
 
That said, we are not familiar with make.com's integration. If you require any further assistance to set up your API calls to work as described above, you will need to reach out to make.com's support team for help with the configuration/setup.

Thanks so much, DB-Des​!

We tried using Zapier (instead of Make.com), and Zapier gives us the option of choosing the "team space".

However, Zapier won't allow us to create new folders at the team root level, which makes it seem like the "Dropbox-API-Path-Root" header isn't set properly.

Do you know if we can set the "Dropbox-API-Path-Root" header using Zapier?

(If we're able to figure out with Zapier, then we might be able to figure it out using Make as well.)

Hi RFrendt​,

You will need to reach out to Zapier support team for assistance on that as well.