---
title: "PUT vs PATCH: when should I use which?"  
description: "PUT vs PATCH: when should I use which?"  
author: "Zeynep Kiliç"  
published: 2026-11-14  
updated: 2026-11-14  
canonical: https://www.mindstick.com/forum/163021/put-vs-patch-when-should-i-use-which  
category: "Web and API Design"  
tags: ["rest api", "put", "PATCH", "HTTP methods", "API Design"]  
reading_time: 1 minute  

---

# PUT vs PATCH: when should I use which?

I only want to change a user's phone number. Should I send PUT with the whole user object or PATCH?

## Replies

### Reply by Dhananjay Prajapati

- **PUT** means "replace this resource with what I send". The client sends the full representation. If a field is missing, it is usually treated as removed or reset.
- **PATCH** means "apply this partial change". The client sends only what changes, such as `{ "phone": "98xxxxxx10" }`.

Both are meant to be repeatable safely. PUT is idempotent by definition (sending it twice gives the same result). A PATCH can be idempotent too, if it sets a value, but not if it means "add 1".

For your case, PATCH is the natural fit, because you change one field. PUT with the whole object risks overwriting changes another user made to other fields.

Many real APIs use PUT loosely for any update. What matters is that you document the behaviour and apply it consistently.


---

Original Source: https://www.mindstick.com/forum/163021/put-vs-patch-when-should-i-use-which

Copyright © MindStick Software Pvt. Ltd. This Markdown version is provided for developers, AI systems, and offline reading.
