Safe methods vs unsafe methods in Rest API - Visual Side-by-Side Comparison

Concept Flow - Safe methods vs unsafe methods

Client sends HTTP request

↓

Check HTTP method type

↓

Safe method?

↓

Read-only action

↓

Return data

↓

Response sent back to client

The client sends a request, the server checks if the HTTP method is safe (read-only) or unsafe (modifies data), then processes accordingly and sends a response.

Execution Sample

Rest API

GET /items
POST /items
GET /items/1
DELETE /items/1

Shows example HTTP requests using safe (GET) and unsafe (POST, DELETE) methods.

Execution Table

Step	HTTP Method	Request URL	Safe Method?	Action Taken	Response
1	GET	/items	Yes	Read list of items	200 OK with items list
2	POST	/items	No	Create new item	201 Created with item info
3	GET	/items/1	Yes	Read item details	200 OK with item details
4	DELETE	/items/1	No	Delete item	204 No Content
5	-	-	-	-	Stop: No more requests

💡 No more requests to process, execution ends.

Variable Tracker

Variable	Start	After 1	After 2	After 3	After 4	Final
items_list	[item1, item2]	[item1, item2]	[item1, item2, new_item]	[item1, item2, new_item]	[item2, new_item]	[item2, new_item]
last_response	None	200 OK with items list	201 Created with item info	200 OK with item details	204 No Content	204 No Content

Key Moments - 3 Insights

Why is GET considered safe even though it returns data?

GET is safe because it only reads data without changing anything on the server, as shown in steps 1 and 3 where data is returned but not modified.

Why are POST and DELETE unsafe methods?

POST and DELETE change the server data (creating or deleting items), shown in steps 2 and 4 where the items_list changes after these requests.

Can a safe method like GET ever modify data?

No, by definition safe methods do not modify data. The execution table shows GET requests only reading data without changes.

Visual Quiz - 3 Questions

Look at the execution table, what is the response after the POST /items request?

A 201 Created with item info

B 200 OK with items list

C 204 No Content

D 404 Not Found

💡 Hint

Check step 2 in the execution_table under the Response column.

At which step does the items_list get an item removed?

A Step 1

B Step 2

C Step 4

D Step 3

💡 Hint

Look at variable_tracker for items_list changes after each step.

If the GET method was changed to POST in step 3, what would happen?

A The server would read item details without changes

B The server would create a new item instead of reading

C The server would delete the item

D The server would return an error

💡 Hint

POST is an unsafe method that modifies data, unlike GET which is safe and read-only.

Concept Snapshot

Safe methods (like GET) only read data and do not change server state.
Unsafe methods (like POST, DELETE) modify data on the server.
Safe methods are idempotent and safe to repeat without side effects.
Unsafe methods can create, update, or delete resources.
Servers handle requests differently based on method safety.

Full Transcript

This visual execution shows how safe and unsafe HTTP methods work in REST APIs. The client sends requests with different methods. Safe methods like GET only read data and return it without changing anything. Unsafe methods like POST and DELETE modify the server data by creating or deleting items. The execution table traces each request step-by-step, showing the method, action, and response. The variable tracker shows how the list of items changes after unsafe methods. Key moments clarify why GET is safe and POST/DELETE are unsafe. The quiz tests understanding by asking about responses and data changes at specific steps. This helps beginners see clearly how safe and unsafe methods behave in real API calls.