Table of Contents
API vs Web Service
In August of 1991, the World Wide Web was born. It was nothing like it is today — in fact, it was slow and quite bare, with hardly any websites online. If you had your own website, you were one of the few out there!
It was even a world before Google. Google didn’t exist until 1998 and most people used Yahoo! to search the web.
As those who were tech-savvy got to know the ins and outs of coding computer languages, we were lucky enough to experience some of the most impressive innovations, available right at our fingertips over the internet.
Suddenly, we were exposed to Google, a search engine that could list everything existing on the World Wide Web.
We had email services that allowed us to talk to other people through a machine — though we later turned to instant messaging services like AIM and MSN. Eventually, websites like Myspace, then Facebook, popped up. These allowed us to create our own Internet versions of ourselves and interact with other people we’d never meet otherwise.
Social media forever changed the way we use the internet. It showed people that we could communicate with each other through a machine at our fingertips — and quickly.
It became clear that the options were limitless. Websites could replace what we do in real life if it was faster and easier.
APIs and Web Services
Source: https://testautomationresources.com/
A web service and an API are two very similar concepts, so it can be difficult to understand the similarities and differences.
Terminology Definition
Before we get started further explaining web services and APIs, we first need to define a few other terms:
- XML [eXtensible Markup Language] is a standardized format for storing and sending data. Similar to HTML, XML stores data by wrapping it in descriptive tags.
- JSON [JavaScript Object Notation] is similar to XML in that it also stores and enables you to send data in a standardized format. JSON just uses a different, object-based, methodology for systematically storing data.
- HTTP [HyperText Transfer Protocol] is the foundation of transferring data and communications on the internet.
- SOAP [Simple Object Access Protocol] is a messaging protocol used for exchanging structured information[XML data] over a network.
- REST [REpresentational State Transfer] is a standardized architectural style that can be used when creating a web API.
- Web applications (Web app) are computer programs that are accessed over the internet through a computer’s web browser.
What is a Web Service?
A Web service is a way for two machines to communicate with each other over a network.
A web server running on a computer listens for requests from other computers. When a request from another computer is received, over a network, the Web service returns the requested resources. This resource could be JSON, XML, an HTML file, Images, Audio Files, etc.
It’s important to note the requirement of the request being made over a network.
What is an API?
An API, or Application Programming Interface, is a set of definitions and protocols that allow one application to communicate with another application.
In general, when we speak about APIs, we are likely speaking about web APIs [APIs that are accessible over the internet]. This is not always the case though. APIs can be exposed through local files (such as a JAR file in a Java program, .H file in C/C++ programs, etc.) to allow two local applications to communicate with each other. This doesn’t require a network as the two applications are communicating within a single device.
Learn more about types of APIs.
So What’s the Difference?
You might be wondering to yourself, APIs and Web services sound like the same thing. It’s a way for two computers to communicate with each other over the internet, right? Well, not quite.
As we mentioned in the section about “What is an API?,” not all APIs are accessible over the internet(a network), while Web Services must always be accessed through a network. That’s the difference right there.
All Web Services are APIs, but not all APIs are Web services.
Is a REST API a Web Service?
The short answer? Yes, REST APIs are a type of Web Service APIs.
A REST API is a standardized architecture style for creating a Web Service API. One of the requirements to be a REST API is the utilization of HTTP methods to make a request over a network.
REST was officially defined by computer scientist Roy Fielding in 2000 during his Ph.D. dissertation. It essentially changed the way applications are built. The implementation of the frontend “client” can be built completely independently from the backend “server.”
A REST request from the client to the server usually consists of the following components:
- URL Path [https://api.example.com/user]
- HTTP Method [GET, PUT, POST, PATCH, DELETE]
- Header – (optional) additional information that the client needs to pass along in the request such as Authorization credentials, Content-Type of the body, User-Agent to define what type of application is making the request, and more]
- Parameters – (optional) variable fields that alter how the resource will be returned.
- Body – (optional) contains data that needs to be sent to the server.
Here’s How the REST API Works:
Let’s say that you want to see what your best friend posted on Instagram. To do this, you need to go on the app and open up your friends Instagram page.
In this example, your Instagram app [the client], would make a request to Instagram’s server [the server] to request your friend’s Instagram profile. This request would be a GET request to the /users endpoint and in the parameters of the request your friend’s account ID would be included.
- HTTP Method: GET
- URL: https://api.instagram.com/v1/users/
- Parameters: user={best_friends_user_id}
[Disclaimer: This is a very simplified example of a request to the Instagram API]
In the same way that you use a GET request to retrieve data, a POST request would be used to create data on a platform. So let’s use the example of posting an image to Instagram. This request would be a POST request to the /media endpoint with a body of the image and parameters with your caption.
- HTTP Method: POST
- URL: https://api.instagram.com/v1/media/
- Parameters: caption={my_great_caption}&user={my_user_id}
- Body: Image to upload
[Disclaimer: This is not an accurate example request to the Instagram API. The post media endpoint is a private endpoint.]
Benefits of REST APIs
The reason REST is so great is that it offers a standardized methodology for making requests to an API. Once you learn one REST API, other REST APIs are going to function in a similar way.
If an API is available over the internet, there is no need to install additional software within your application. You can access the data from any application that is connected to the same network as the API.
With separated development on the client and server, the client code can be updated without affecting the server, and the server code can be updated without affecting the server. This is assuming the changes are developed in a backwards compatible way.
The Core Differences
If you got a little lost reading about APIs and web services, here is a quick summary of what we covered above.
- APIs are application interfaces, meaning that one application is able to interact with another application in a standardized way.
- Web services are a type of API, which must be accessed through a network connection.
- REST APIs are a standardized architecture for building web APIs using HTTP methods.
We hope that this article has helped you sort through the differences, ins and outs, and general information you may need to know for an API and Web service.
Get Started with APIs
Ready to begin working with APIs? Start browsing over 10,000 APIs within RapidAPI’s API Marketplace and test API calls right in the browser. Build something awesome today!
Get Started Now
Leave a Reply