About Greg K.

It sounds like you're using a Business team with the new team space and member folders configuration that some teams have access to.   That being the case, you'll need to specify the team folder specifically when making API calls to access its contents, for example, by supplying the 'Dropbox-API-Path-Root' header. You can find more information on that here:   https://www.dropbox.com/developers/reference/namespace-guide   The Dropbox API Explorer is built for the older configuration, but we're working on updating the API and SDK support and documentation to support the new one. That's not quite ready yet though, so unfortunately there isn't a good way to use the API Explorer for this right now, but you can run it outside the of Explorer. Apologies for the inconvenience! ... View more

That's correct, the client secret is required for the code flow. If you want to use the token flow, you can use response_type=token and redirect_uri=https://www.dropbox.com/1/oauth2/display_token (as long as you register "https://www.dropbox.com/1/oauth2/display_token" for your app). The token flow doesn't require the client secret, and the display_token page will just show the access token itself to the user for copy/pasting it. ... View more

The special "app folder" created for an app with the "app folder" permission is only accessible to the user that connected the app (you, in this case). This is the same regardless of your account plan (free, paid, Business, etc.) as well as the app's status (development vs. production). It's unfortunately not possible to share the app folder with others. If you need to have the app interact with shared folders, you'd need to create an app with the "full Dropbox" permission instead, so that can create and share arbitrary folders. ... View more

Thanks! That's the error from the API, and it does indicate that the issue is that the contents of the request body couldn't be successfully decoded as JSON.   It sounds like the issue is with encoding these characters. That's generally done automatically, but that doesn't seem to be the case with PowerShell/Invoke-RestMethod.   I'm not a PowerShell expert, and it also looks like copying it onto the forum didn't work right here, but I believe you need to additionally encode the body like this:   $enc = [System.Text.Encoding]::UTF8 $body = $enc.GetBytes($body) ... View more