The reason we ask people to contact our support humans by email is because every member of our dedicated, full-time support team are already quite busy with the email traffic they’re handling. They need every bit of efficiency we can send their way to stay on top of it all. With email messages, we can assign each message a ticket number and we have a system in place which lets them claim tickets so we don’t have two people working on the same ticket at the same time, etc.
Our forums and Slack don’t have any such system for distributing work among our support team, and most messages posted here wouldn’t be intended for our support team anyway. It’s simpler and more efficient to segregate our support traffic completely—which is why our welcome messages both for these forums and for Slack direct people to use email if they’re trying to contact our support team.
Now, that said, I certainly agree that some of our support team’s responses will be of interest to other users! You’re more than welcome to share answers you receive from our support team back on these forums.
(As for your specific question: Sal actually did write that content quite some time ago, but then heard from our engineering team that those APIs weren’t ready for prime time yet and the documentation shouldn’t be published until they’re ready. We didn’t hear much feedback through our support channels asking for this functionality, so it’s fallen off our priority list in favor of the things we do hear about every day. But if people who are interested in this reach out to support and ask about it, that feedback will make it to our development teams where it can help guide our development priorities and roadmap. So if this is a capability you’re interested in, that’s another good reason to reach out to us by email!)
