But what if you then want to switch to another API provider? Maybe the one you were using isn't accessible, doesn't support the older browsers you need? Maybe they put their prices up? Whatever the reason you may need to switch at some point.
There is a better way.
Rather than working directly with an API and using the properties and methods in your code, you create an intermediary, your own internal service, which handles this functionality. The internal service maps the properties and methods you need to those of the third party API. It handles any data transformation needed. Your app works with this service, your own API, so that when a change of service provider is needed the app itself does not need to be rewritten, just the internal service.
An internal service can also be set up to work with multiple APIs at once so it maps everything it needs for each. This allows you to push choice to your users. So, for example, if it's a news, sport or weather feed built into a site, you can let your user choice their preferred information source. You could use different services for different regions, e.g. local news.
To use a slightly inappropriate analogy, it's better to be dating these APIs than to move in with them. 😉