Conversely I just implemented Google OAuth, though all I did was use some of the Google Plus APIs, and it was very straight forward (one oddity though was entir

Conversely I just implemented Google OAuth, though all I did was use some of the Google Plus APIs, and it was very straight forward (one oddity though was entirely different domains for retrieving the access code (used for getting the access token) vs. retrieving the access token (used for making API requests)) [1]. Some of the APIs are superbly documented with a lot of obvious effort put into them. Google sheets sounds like it isn't. I think one major problem is that there is a unified interface and docsets for both the good APIs and the bad APIs - while there are starkly different teams maintaining them with different interests and motivations. APIs that make a ton of money for Google are naturally going to get more love, the reverse will likely be abandoned, inaccurate, etc. The bottom line we have to remember as developers is that we use Google's API at their own discretion. Many popular used APIs are "FREE". If you want to create a stable, long-term, software product, you need to think long and hard about incorporating third party APIs, no matter if it's provided by a large well-respected organization like Google, or the teenager down the street. [1]: "https://accounts.google.com/o/oauth2/v2/auth" https://accounts.google.com/o/oauth2/v2/auth", "https://www.googleapis.com/oauth2/v4/token" https://www.googleapis.com/oauth2/v4/token",