PATCH for partial updates in Rest API - Step-by-Step Execution

Concept Flow - PATCH for partial updates

Client sends PATCH request

↓

Server receives PATCH request

↓

Server reads partial data to update

↓

Server updates only specified fields

↓

Server saves changes

↓

Server sends response with updated resource

↓

End

The client sends a PATCH request with only the fields to update. The server updates those fields without changing others, then responds with the updated resource.

Execution Sample

Rest API

PATCH /users/123 HTTP/1.1
Content-Type: application/json

{"email": "[e-mail]"}

Client sends a PATCH request to update only the email field of user 123.

Execution Table

Step	Action	Data Received	Fields Updated	Server Response
1	Receive PATCH request	{"email": "[e-mail]"}	None yet	None yet
2	Parse JSON body	{"email": "[e-mail]"}	None yet	None yet
3	Find user 123 in database	User data before update	None yet	None yet
4	Update email field only	Email field value	email	None yet
5	Save updated user data	User data with new email	email	None yet
6	Send response with updated user	User data with new email	email	200 OK with updated user JSON
7	End	None	None	Response sent

💡 PATCH request processed; only specified fields updated; server responded with updated resource.

Variable Tracker

Variable	Start	After Step 4	After Step 5	Final
user_data	{"name": "Alice", "email": "[e-mail]", "age": 30}	{"name": "Alice", "email": "[e-mail]", "age": 30}	{"name": "Alice", "email": "[e-mail]", "age": 30}	{"name": "Alice", "email": "[e-mail]", "age": 30}

Key Moments - 3 Insights

Why does PATCH update only some fields and not replace the whole resource?

Because PATCH is designed for partial updates, the server updates only the fields sent in the request (see execution_table step 4), leaving other fields unchanged.

What happens if the PATCH request body is empty?

The server receives no fields to update (execution_table step 2), so no changes are made and the original resource is returned.

How does the server know which user to update?

The user ID is specified in the URL (e.g., /users/123), so the server finds the correct user before updating (execution_table step 3).

Visual Quiz - 3 Questions

Look at the execution table, at which step does the server update the email field?

A Step 4

B Step 2

C Step 5

D Step 6

💡 Hint

Check the 'Fields Updated' column in the execution_table rows.

According to the variable tracker, what is the user's email after step 5?

A "[e-mail]"

B null

C "[e-mail]"

D Not updated yet

💡 Hint

Look at the 'user_data' row under 'After Step 5' in variable_tracker.

If the PATCH request included the 'age' field, how would the execution table change?

A No change, only email is updated

B Fields Updated would include 'email' and 'age' at step 4

C Server would reject the request

D Response would be empty

💡 Hint

Refer to how 'Fields Updated' is shown in execution_table step 4.

Concept Snapshot

PATCH request updates only specified fields of a resource.
Client sends partial data in request body.
Server merges changes without replacing whole resource.
Response returns updated resource.
Used for efficient partial updates in REST APIs.

Full Transcript

PATCH is a method in REST APIs used to update only parts of a resource. The client sends a PATCH request with just the fields to change. The server finds the resource, updates only those fields, saves the changes, and sends back the updated resource. This avoids sending or replacing the entire resource. For example, updating only a user's email without changing their name or age. The execution table shows each step from receiving the request to sending the response. The variable tracker shows how the user data changes only in the email field. Common confusions include why PATCH updates partially, what happens if no fields are sent, and how the server identifies which resource to update. The visual quiz tests understanding of these steps and changes.