Why did web services become called API or what is the difference between them?

Question

Web development

In recent years, often web services (usually RESTful or curved REST-like, SOAP / XML-RPC much less often) often call HTTP / REST API or just API. Is there any logic in this or is it just a fashion?

PS: Just in case, I'll clarify what "API" is, in principle, I've known since the dawn of the Win32 API :-)

Answer 1

1) old-school (SOAP/XML) web services were called so because there is a group of standards from the W3C, and the concept of "web service" is used there ( https://www.w3.org/TR/ws-arch/#id2260892 );
2) that's why REST APIs are named to be more different from web services, and at the same time to emphasize that in such interaction the only standard "for all" is HTTP. Everything else - request / response formats, the degree of compliance with the REST architecture - is determined by a specific service, and therefore I wanted some kind of "lightweight" term that would talk about such interaction contracts that work on top of HTTP and correspond to the REST architecture. Therefore, REST API / Web API , which translates as "a contract that works on top of HTTP in accordance with the Web architecture."

Answer 2

Well, in fact, everything is an API. Even a regular http site is also an API for the browser.
I think it's fashion in general.
I can make API not via http, soap, etc. and it will still be an API.

Answer 3

Many customers understand by API not even an API at all.
I understand this trick, and I always write to customers "I'm making a cool API for your requirements." Bullshit? Works!
Kill everyone. API is stylish, fashionable, youthful. Everyone makes an API, and I will make an API.
If a customer needs an API for a feedback form that will send SMS to him, I will make such an API for him.
Terms for seniors.

Answer 4

The web service has an API. Fashion has nothing to do with it, in some context it is more convenient to say API, in another web service.