Definitely true. APIs aren&#x27;t standard, they aren&#x27;t guaranteed, and they require constant vigilance from the consuming app&#x27;s POV. Notably though, these aren&#x27;t mostly paid APIs. If its free data, then the developers should do what they think best presents the free data they are giving away.<p>On the other hand, if you want a great example of how to do it right, salesforce.com has a pretty great API strategy. rather than try for some &quot;version-less ideal&quot; API, they release new versions and new endpoints, and have only ever deprecated old APIs for security reasons.<p>I suspect that when APIs are changing all the time, it is because the API&#x27;s implementation is too close to the underlying application or data structure. In an ideal state, the APIs are only supposed to present data in a certain way, and shouldn&#x27;t necessarily be determined by the actual structure of that data in an application or database.