Why REST APIs exist - Visual Breakdown

Concept Flow - Why REST APIs exist

Client needs data or action

↓

Client sends request to Server

↓

Server processes request

↓

Server sends response back

↓

Client uses response data

↓

Repeat for different clients and servers

↓

REST API standardizes this process

This flow shows how clients and servers communicate using REST APIs to exchange data and perform actions in a simple, standardized way.

Execution Sample

Rest API

GET /users/123 HTTP/1.1
Host: example.com

Response: 200 OK
{
  "id": 123,
  "name": "Alice"
}

A client asks the server for user data with ID 123, and the server replies with the user's information.

Execution Table

Step	Action	Details	Result
1	Client sends request	GET /users/123	Request sent to server
2	Server receives request	Reads GET /users/123	Understands client wants user 123
3	Server processes request	Fetch user 123 data	User data found
4	Server sends response	200 OK with user JSON	Client receives user data
5	Client uses response	Displays user info	User info shown to user
6	Repeat	Other clients or requests	Same process standardized by REST

💡 Process stops after client receives and uses the server response

Variable Tracker

Variable	Start	After Step 1	After Step 3	After Step 4	Final
Request	None	GET /users/123	GET /users/123	Sent to server	Used by client
Response	None	None	User data ready	200 OK with JSON	Received and used
UserData	None	None	{"id":123,"name":"Alice"}	{"id":123,"name":"Alice"}	Displayed

Key Moments - 3 Insights

Why does the client send a request instead of directly accessing data?

The client and server are separate; the client must ask the server for data using requests, as shown in execution_table step 1.

Why is the response formatted in JSON?

JSON is a simple, standard format that both client and server understand, making data exchange easy, as seen in execution_table step 4.

What makes REST APIs different from other communication methods?

REST APIs use standard HTTP methods and formats so many clients and servers can communicate easily, shown by the repeated process in step 6.

Visual Quiz - 3 Questions

Look at the execution_table, what does the server do at step 3?

A Sends the response to the client

B Processes the request and fetches user data

C Client displays the user info

D Client sends the request

💡 Hint

Check the 'Action' and 'Details' columns at step 3 in execution_table

At which step does the client receive the user data?

A Step 2

B Step 5

C Step 4

D Step 1

💡 Hint

Look for when the server sends the response and client receives it in execution_table

If the server did not use a standard format like JSON, what would change in the process?

A Client might not understand the response easily

B Server would not process requests

C Client would not need to send requests

D Client would send more requests

💡 Hint

Refer to key_moments about why JSON is used for easy understanding

Concept Snapshot

REST APIs let clients and servers talk using simple requests and responses.
Clients ask for data or actions; servers reply with data.
They use standard HTTP methods and formats like JSON.
This makes communication easy and works for many devices.
REST APIs exist to make data sharing simple and universal.

Full Transcript

REST APIs exist to help different devices and programs talk to each other easily. The client sends a request to the server asking for data or to do something. The server reads the request, processes it, and sends back a response with the needed data or confirmation. This process uses standard ways like HTTP methods and JSON format so everyone understands each other. This makes it simple for many clients and servers to work together without confusion.

Practice

1. Why do REST APIs exist in software development?

easy

A. To allow different programs to communicate over the internet using simple rules

B. To create complex user interfaces for websites

C. To store data only on local machines

D. To replace all programming languages with one standard

Solution

1. Step 1: Understand the purpose of REST APIs

   REST APIs are designed to let different software programs talk to each other over the internet easily.

2. Step 2: Compare options with this purpose

   Only To allow different programs to communicate over the internet using simple rules correctly describes this purpose. Options A, B, and C do not relate to REST APIs' main goal.

3. Final Answer:

   To allow different programs to communicate over the internet using simple rules -> Option A

4. Quick Check:

   REST APIs exist for communication = D [OK]

Hint: REST APIs help programs talk over the internet simply [OK]

Common Mistakes:

• Thinking REST APIs create user interfaces
• Believing REST APIs store data locally only
• Assuming REST APIs replace programming languages

2. Which HTTP method is commonly used in REST APIs to retrieve data from a server?

easy

A. GET

B. POST

C. DELETE

D. PUT

Solution

1. Step 1: Recall HTTP methods in REST APIs

   GET is the method used to request and retrieve data from a server.

2. Step 2: Match the method to the action

   POST sends data, DELETE removes data, PUT updates data. Only GET retrieves data.

3. Final Answer:

   GET -> Option A

4. Quick Check:

   Retrieve data = GET [OK]

Hint: GET means get data from server in REST APIs [OK]

Common Mistakes:

• Confusing POST with GET for data retrieval
• Using DELETE or PUT to get data
• Not knowing HTTP method purposes

3. What will be the output of this REST API call?

GET /users/123

Assuming user 123 exists and the API returns JSON data.

medium

A. 500 Internal Server Error

B. {"id":123,"name":"Alice"}

C. 404 Not Found

D. {"error":"User not found"}

Solution

1. Step 1: Understand the GET request to /users/123

   This request asks the server for data about user with ID 123.

2. Step 2: Check the condition given

   The user 123 exists, so the server returns the user's data in JSON format.

3. Final Answer:

   {"id":123,"name":"Alice"} -> Option B

4. Quick Check:

   Existing user GET returns data = C [OK]

Hint: GET existing user returns JSON data, not error [OK]

Common Mistakes:

• Choosing error responses when user exists
• Confusing 404 with successful data return
• Not recognizing JSON format

4. Identify the error in this REST API usage:

POST /users/123

What is wrong if the goal is to update user 123's data?

medium

A. The URL should not include the user ID

B. GET method should be used to update data

C. POST is used instead of PUT for updating existing data

D. DELETE method is required to update data

Solution

1. Step 1: Understand HTTP methods for REST APIs

   POST is usually for creating new data, PUT is for updating existing data.

2. Step 2: Match method to action

   Since the goal is to update user 123, PUT should be used instead of POST.

3. Final Answer:

   POST is used instead of PUT for updating existing data -> Option C

4. Quick Check:

   Update needs PUT, not POST = B [OK]

Hint: Use PUT to update existing data, not POST [OK]

Common Mistakes:

• Using POST to update instead of PUT
• Thinking GET updates data
• Believing DELETE updates data

5. You want to design a REST API that allows clients to list all products and add new products. Which HTTP methods and URLs should you use?

hard

A. DELETE /products to list, PUT /products to add new

B. POST /products to list, GET /products to add new

C. PUT /products to list, DELETE /products to add new

D. GET /products to list, POST /products to add new

Solution

1. Step 1: Identify methods for listing and adding

   GET is used to retrieve or list data, POST is used to create or add new data.

2. Step 2: Match methods with URLs

   Both actions use the /products URL; GET lists products, POST adds new products.

3. Final Answer:

   GET /products to list, POST /products to add new -> Option D

4. Quick Check:

   List = GET, Add = POST = A [OK]

Hint: GET lists, POST adds new resources in REST APIs [OK]

Common Mistakes:

• Swapping GET and POST roles
• Using DELETE or PUT incorrectly
• Confusing URLs for different actions