API (Application Programming Interface) Vs REST API (Representational State Transfer API)


API (Application Programming Interface)
API is an abbreviation for application programming interface, which is a collection of specifications and protocols for developing and integrating application software.

Client and server are commonly used to describe API architecture. The programmer that sends the request is known as the client, and the application that sends the answer is known as the server.

API (Application Programming Interface)
Fig 1.1- API Calls

APIs are widely used and approved in online applications. APIs are classified into four kinds that are typically used in online services: public, partner, private, and composite.

Four different ways that APIs and one of them is REST API

REST API (Representational State Transfer API)
These APIs are referred to as Remote Procedure Calls. The client performs a function (or operation) on the server, and the server returns the result to the client.

REST specifies a set of methods that clients may use to access server data, such as GET, PUT, DELETE, and so on. HTTP is used by clients and servers to exchange data.

The statelessness of REST APIs is a key characteristic. Servers that are stateless do not save client information between requests. Similar to the URLs you put into your browser to view a website, client requests to the server. The server's response is just basic data without the customary graphical web page display.

Fig 1.2- API vs REST API

In conclusion, a REST API is a kind of API that uses HTTP for communication, adheres to a certain architectural style, and enables the creation, reading, updating, and deletion of resources via the internet.

Continue Reading..
API calls and Security - The Network DNA
Cisco SDWAN: vManage and Netconf - The Network DNA
Cisco DNA Center: Use of TACACS for Netconf - The Network DNA
Introduction to RESTful API for vManage NMS - The Network DNA

No comments