Disable desktop notifications for app's folder

And what about the "mute" parameter of the files/upload method. Steve M. seems to recall some limitations. What are they?

We don't have any more specific documentation, but I expect Steve was referring to older versions of the desktop client possibly not supporting the behavior, and perhaps some special logic beyond the parameter itself that determines whether or not to mute the notification. (E.g., it might make sense to show a notification regardless, even if mute was set, if there was a conflict.) I'll send this along as feedback to get this better documented though.

So basically, it works as intended? As long as the user uses an up to date client and there is nothing he should be aware of, no notification is shown?

I haven't tried it out myself recently, but if you give it a try and it doesn't behave as expected, please let me know and I will bring it up with the team.

Hi Gregory, thank you for your answer, very appreciated. Am I right in the statement that this would require a simple change in the DropBox desktop client(s)? Can you please share your opinion on this question here? When you say "I don't have any news", does it mean you have absolutely a zero chance to contact your other departments/colleagues/internal systems?

Thank you for keeping up with this Jan. I've been following this closely. I can't believe it's not a feature that is available in the Dropbox app itself. And if this is the wrong forum (yeah it's the API forum but the only question that was up when I originally looked), why is it so difficult to pass it along to another team?

No, I don't expect it would necessarily be a simple change.

When I say I don't have any news, I mean that I don't have any announcement about this request potentially being implemented and released.

I have certainly contacted the team and opened this as a feature request with them.

"I don't have any announcement about this request potentially being implemented and released."

And I thought it was solved by the "mute" parameter...

To be clear, I had a working implementation with Dropbox Sync. Because of this issue, I didn't bothered trying to update it to use the API v2 and moved on. I won't spend the time updating to the v2 if the issue is the same.

The stable API doc states that this "mute" flag is doing exactly what we're asking for: "mute Boolean Normally, users are made aware of any file modifications in their Dropbox account via notifications in the client software. If True, this tells the clients that this modification shouldn't result in a user notification. The default for this field is False."

So I thought I'll give it a try after all. But then, they might eventually be some possible limitations sometimes, then not really but try yourself, and then, this is potentially not implemented? Why is it so difficult to make a clear and definitive statement?

▢ The API works as intended, the issue is closed.

▢ The API has some bugs with the "mute" flag. They will be addressed.

▢ The "mute" flag does something completely different from what's stated in the documentation. A feature request has been opened.

Thomas, to clarify, there were essentially two different forms of this feature request. One is a way to mute notifications on a case-by-case basis, which we added to API v2 via the mute parameter. 

The other is to just mute all of the notifications for items the Apps folder, which hasn't been implemented and is considered an open feature request.

Thanks for passing along the mute Apps folder request, Gregory. Much appreciated.