About Greg K.

When you create folder or upload files using the API, there are a number of ways to specify where you want to put the folders/files. By default, these operations will work inside the user's own folder, and not in a shared folder or space. I recommend reading the Namespace Guide and Content Access Guide, as they cover how these mechanisms work and what options you can control from the API.  On the Business Admin Console, a team admin can view always view shared team content, but they won't see content inside individual team member folders by default. Some Business plans do offer an additional "sign in as" feature that enables them to access individual member accounts though.  ... View more

No problem, thanks for confirming. Anyway, yes, I meant adding a new 10 second delay before the next  /2/sharing/share_folder call. ... View more

Apologies, I'm not sure I follow. In your original message, the error output you shared appears to be from the response to a call to /2/sharing/check_share_job_status (for checking the job started by calling /2/sharing/share_folder). In your latest message though, you just said you're getting an error from /2/sharing/add_folder_member. Was that a typo, or are you also getting errors from /2/sharing/add_folder_member? If it's the latter please share a sample of that. Thanks! ... View more

Thanks for the additional information. I see you have extra  \ values in your JSON string. You may have copied those from the command-line curl examples in the documentation. Those are only needed in contexts where you need to escape the subsequent " values, such as in bash, like in those examples, since the " character is already used to start the string for the header parameter for curl itself. Since that doesn't apply to your PHP context, you shouldn't include them as they'll be sent as-is, corrupting the JSON string. Instead, you'd just want something like: $headers[] = 'Dropbox-Api-Arg: {"path": "/test"}'; I do recommend having some other library or method build those JSON strings for you instead though. ... View more

The /2/files/download endpoint is a "content-download" style endpoint, so it expects the parameters (such as "path") as JSON in a 'Dropbox-API-Arg' request header.  This "could not decode input as JSON" error indicates that the value supplied in the 'Dropbox-API-Arg' request header could not be successfully parsed, likely because it is not valid JSON. Please check that you're supplying a valid JSON string in the 'Dropbox-API-Arg' request header. If you're not already using one, we recommend using a JSON library for reading/writing the JSON strings, instead of doing so manually. You can also use the API v2 Explorer to prototype these calls for you. It will build the header for you, and can even show you the code for making the call. If something still isn't working as expected, please share the relevant code and output (but please redact your access token). ... View more