When calling the `sharing/share_folder` endpoint with a path that contains disallowed characters, for example that ends with a backslash "\", the endpoint won't return a WriteError (malformed_path) but rather a HTTP error 500 (internal Dropbox error). This is not particularly helpful since it does not allow us to distinguish between actual backend errors and invalid input.
According to the documentation on Team Spaces and looking at the actual behaviour of the `sharing/share_folder` endpoint, a call with a non-existing path will create the specified folder. I would therefore expect that similar `WriteError`s as for `files/create_folder` should be returned in some cases.
If you'd like to look into the actual requests which I made to test this, the latest request id is
52e7070699b94a88a1a1e7c47655d11a.
