Hey @chroventer the problem we have is that the current API endpoints are too risky for us to publicize as they are. They’re not designed to handle arbitrary requests from the world wide web; just to handle carefully constructed ones from within our own systems.
We have tasks in our backlog to design a community-facing API that we can fully document and support long-term, but until that’s ready we don’t have anything we’re comfortable telling the community about. When we do have something ready we’ll surely announce it in the Forums (along with wherever else seem appropriate).