I can sympathize, We all have these travails...
I have the problem with amazon MWS all the time vs. eBay and NewEggs APIs....
They don't document at all, have no centralized organized place for there published revision history and don't inform anyone in advance about up coming changes that will break your software.

I find that people designing and programming in the B.S. Agile environments like Scrum make the worst design and technical support documents, plus alot of spaghetti bloatware.

That's the major disadvantage of decentralized open source projects for the most part.
There is a lack of a uniform vision that guides the product path, and internal and external documentation is a complete afterthought. That's why it's a mess an tough to figure out most of the time. Even for a guy like me who has written case tools, compilers, worked for hundreds of companies and knows at least 100 languages and, frameworks.

Committees are great for codifying standards after a shake out.
But during design and development the old saying "to many cooks spoil the broth comes into play".

Just my sense for someone who's been in the field since 1980. Yea this old dog has some bite...

on another been working on a group app for my team....
calling it the SteemConsole here's a screen shot (pre-alpha)....about to add a second status button that opens another tab that brings up your site for the user.

LMK if you'd like to get an Alpha Copy...