PATCH for partial updates in Rest API

Introduction

PATCH lets you change only some parts of data without sending everything again. It saves time and data.

You want to update just the email address of a user without changing other details.

You need to fix a typo in a product description without resending the whole product info.

You want to mark a task as done without changing its title or deadline.

You want to update the status of an order without resending customer info.

Syntax

Rest API

PATCH /resource/{id}
{
  "field_to_update": "new_value"
}

PATCH requests include only the fields you want to change.

The server updates those fields and keeps the rest unchanged.

Examples

Update only the email of user with ID 123.

Rest API

PATCH /users/123
{
  "email": "[e-mail]"
}

Mark task 456 as completed without changing other details.

Rest API

PATCH /tasks/456
{
  "completed": true
}

Sample Program

This Python code sends a PATCH request to update only the phone number of user 123. It prints success or failure and shows updated data.

Rest API

import requests

url = 'https://api.example.com/users/123'

# Data to update only the phone number
patch_data = {
    "phone": "[phone]"
}

response = requests.patch(url, json=patch_data)

if response.status_code == 200:
    print('Update successful')
    print('Updated user data:', response.json())
else:
    print('Update failed with status:', response.status_code)

Important Notes

PATCH is different from PUT, which replaces the whole resource.

Always send only the fields you want to change with PATCH.

Some servers may not support PATCH; check API docs.

Summary

PATCH updates parts of data without sending everything.

Use PATCH to save bandwidth and time when changing small details.

Send only the fields you want to update in the PATCH request body.

Practice

1. What is the main purpose of using the PATCH method in REST APIs?

easy

A. To update only specific fields of a resource without sending the entire data

B. To create a new resource on the server

C. To delete a resource completely

D. To retrieve data from the server

Solution

1. Step 1: Understand HTTP methods

   HTTP methods like GET, POST, PUT, DELETE, and PATCH have different purposes. PATCH is designed for partial updates.

2. Step 2: Identify PATCH behavior

   PATCH sends only the fields that need to be changed, unlike PUT which requires the full resource data.

3. Final Answer:

   To update only specific fields of a resource without sending the entire data -> Option A

4. Quick Check:

   PATCH updates parts only [OK]

Hint: PATCH updates parts, not whole resource [OK]

Common Mistakes:

• Confusing PATCH with PUT which replaces full resource
• Thinking PATCH creates new resources
• Using PATCH to delete resources

2. Which of the following is the correct way to send a PATCH request to update a user's email using JSON?

easy

A. PATCH /users/123 {"email": "[e-mail]"}

B. PATCH /users/123 {"username": "newuser"}

C. GET /users/123 {"email": "[e-mail]"}

D. DELETE /users/123 {"email": "[e-mail]"}

Solution

1. Step 1: Identify HTTP method and endpoint

   PATCH is used to update part of the resource at /users/123.

2. Step 2: Check JSON body for correct field

   The JSON body contains only the field to update, here "email" with new value.

3. Final Answer:

   PATCH /users/123 {"email": "[e-mail]"} -> Option A

4. Quick Check:

   PATCH + partial JSON body = correct syntax [OK]

Hint: PATCH with only fields to update in JSON body [OK]

Common Mistakes:

• Using GET or DELETE instead of PATCH
• Sending unrelated fields in PATCH body
• Trying to update username when email is asked

3. Given this PATCH request body to update a product:

{"price": 19.99}

What will be the result if the original product data was

{"name": "Book", "price": 25.00, "stock": 10}

?

medium

A. {"name": "Book", "price": 25.00, "stock": 10}

B. {"price": 19.99}

C. {"name": "Book", "price": 19.99, "stock": 10}

D. {"name": "Book", "stock": 10}

Solution

1. Step 1: Understand PATCH partial update

   PATCH updates only the fields sent, here "price" changes to 19.99.

2. Step 2: Combine unchanged fields with updated field

   Fields not in PATCH body remain unchanged, so "name" and "stock" stay the same.

3. Final Answer:

   {"name": "Book", "price": 19.99, "stock": 10} -> Option C

4. Quick Check:

   PATCH updates price only, others unchanged [OK]

Hint: PATCH changes only sent fields, keeps others [OK]

Common Mistakes:

• Replacing entire object instead of partial update
• Removing fields not in PATCH body
• Ignoring updated field in result

4. You send this PATCH request to update a user's profile:

{"email": "[e-mail]", "age": "twenty"}

The server expects age as an integer. What is the likely problem?

medium

A. The PATCH request will succeed and update both fields

B. The server will delete the age field from the user profile

C. The server will ignore the age field and update only email

D. The server will reject the request due to invalid data type for age

Solution

1. Step 1: Check data types in PATCH body

   "age" is sent as string "twenty" but server expects integer.

2. Step 2: Understand server validation

   Most servers validate data types and reject requests with invalid types.

3. Final Answer:

   The server will reject the request due to invalid data type for age -> Option D

4. Quick Check:

   Invalid data type causes rejection [OK]

Hint: Check data types match server expectations [OK]

Common Mistakes:

• Assuming server auto-converts wrong types
• Thinking PATCH ignores invalid fields silently
• Believing PATCH deletes fields on error

5. You have a REST API for managing tasks with fields: title, completed, and priority. You want to mark a task as completed without changing other fields. Which PATCH request body is best?

hard

A. {"title": "", "completed": true, "priority": null}

B. {"completed": true}

C. {"completed": true, "priority": "high"}

D. {"title": "New Task"}

Solution

1. Step 1: Identify minimal update needed

   Only the "completed" field needs to change, so send only that.

2. Step 2: Avoid sending unrelated or empty fields

   Sending empty or null fields may overwrite data unintentionally.

3. Final Answer:

   {"completed": true} -> Option B

4. Quick Check:

   Send only changed fields in PATCH body [OK]

Hint: Send only fields you want to update in PATCH [OK]

Common Mistakes:

• Sending all fields even if unchanged
• Sending empty or null values accidentally
• Using PUT instead of PATCH for partial update