What is REST API

A REST API (short for Representational State Transfer Application Programming Interface) is a set of rules for how two computer systems talk to each other over the internet. It’s not one specific API, but a style of building APIs; one that’s become the most common for web-based systems.

In plain terms, REST APIs let different software applications send and receive data using the same web technology your browser uses to load websites (HTTP). When you interact with a mobile app or website (like adding something to your shopping cart or checking delivery status) it’s probably using a REST API in the background to make that happen.

A brief history

APIs have existed for decades, originally to help different pieces of software talk inside the same computer. But as the internet grew in the 1990s, developers needed a better way for systems to communicate over the web.

In 2000, computer scientist Roy Fielding introduced REST as a simpler, more scalable way to build APIs using existing web technologies. Compared to earlier approaches (like SOAP, which was more rigid and complex), REST was lightweight and easier to adopt. It quickly became the go-to approach for building APIs that power web and mobile apps.

How it fits into your tech stack

REST APIs use web addresses (URLs) to access resources like products, users, or orders. To interact with those resources, they use standard HTTP methods:

  • GET: Retrieve information
  • POST: Add something new
  • PUT: Update something
  • DELETE: Remove something

The data being sent or received is usually in JSON format, which is easy for both humans and machines to understand.

Know more

Frequently Asked Questions

What exactly is a REST API?
A REST API is a way to build APIs using simple web rules. It’s not one specific API; it’s a style or standard that developers follow when creating APIs for web-based systems.
What are the main REST “commands”?
The most common REST “commands” are: GET: Get some data (like a product description) POST: Add something new (like a new product) PUT: Update something (like changing a product price) DELETE: Remove something (like deleting a product listing)
What is a “stateless” API, and is REST one?
A stateless API doesn’t store any information about previous requests. Each time you send a request, it has to include everything the server needs to process it, like who you are and what you’re asking for. REST APIs are designed to be stateless, which makes them easier to scale and more predictable, since each request stands on its own.
Is a REST API secure?
REST APIs can be secure! They typically use methods like API keys or tokens to make sure only authorized users or systems can access or change data.
Can REST APIs send live updates?
REST APIs aren’t the best choice for live updates; they’re best for requesting or sending data on demand. For real-time updates (like notifications), other tools like webhooks or WebSockets are better suited.
Are there other ways to build APIs besides REST?
Yes! REST is popular, but not the only option. Other types include: GraphQL: Lets you request exactly the data you want in a single call SOAP: An older, more structured type of API gRPC: A high-performance option often used in backend systems