I wouldn't phrase it exactly that way. All the examples are of something much more specific: APIs go away when a company embraces an advertising-driven revenue model.
Google offered a SOAP API because back then they weren't an ad company. When they became an ad company the API went away, because you could use it to get Google search results without the ads. Twitter supported third-party clients because back then they weren't an ad company. When they became an ad company the API went away, because you could use it to read tweets without seeing the ads.
Once you decide your company is going to make its money via ads, the strangulation of any channel people can use to get to your service without seeing the ads inevitably follows.
Or not.
* Google Hangouts
* SMS
* iMessage (cost prohibitive)
When really I should just be able to log into xmpp.voltagex.org and talk to everyone.
(Also, why isn't there a standard for "dialling" email addresses yet?)
Basically the same reason that little is available via RSS these days, and what is always has the "click here to read the whole article on our site, where we can show you ads!" after a few sentences / paragraphs.
There are SMS services who support XMPP, and additionally Facebook and Hangouts support the XMPP client-side. It’s not as convenient as sending from [email protected] a message to [email protected], but it still works quite nice.
Looks like it is yeah
This isn't so cut and dry. iTunes offers database dumps, for free, to any developer building music discovery sites and apps: this is why virtually everything has a "buy this on iTunes" button. Walmart has an API for people who want to add "buy this from Walmart", as does Amazon (also Best Buy and Sports Mart, but they are not clearly dominating like Walmart and Amazon in their respective markets). There has to be something different about how this plays out for Netflix than for these other companies.
Google once allowed search queries via a SOAP interface. That's gone. They also dropped RSS feeds. But the API for submitting paid ads, that works. The paid cloud services are fine.
Twitter doesn't like third party Twitter clients any more and will pull the API key of anyone who writes one. A third party client might have a spam ("sponsored tweet") filter.