Understanding POST, PUT, and PATCH HTTP Methods

Study Session by: [email protected] — October 8, 2026 — 5m

Sign up to Cognizoro
HTTP MethodsREST APIsWeb DevelopmentPOST PUT PATCH
Conversation
Quizzes (1)
Flashcards (0)
Notes (0)
Weakness Insights (0)
Hey, can you tell me the difference between Post, Put, Patch in application development. Please give me some examples too

Hello! I would love to explain this.

To understand POST, PUT, and PATCH, let's imagine you are playing a video game where you can create and customize your own character.

Your character has a profile that looks like this:

  • Name: Alex
  • Level: 5
  • Hat: Blue Cap
  • Shoes: Red Sneakers

Now, how does your game talk to the server to save or change this character? That is where these three HTTP actions come in!

1. POST: "Create Something Brand New"

Think of POST like pressing the "Create New Character" button.

  • What it does: It sends brand-new information to the server to create a new record from scratch.
  • Real-world analogy: You fill out a blank registration form at a library. You hand it to the librarian, and they assign you a brand-new card number.
  • Game example: You create a second character named "Sam". The server saves Sam as a new player and gives them a brand-new ID number.
  • Key idea: If you click "POST" three times, you will end up with three different characters.

2. PUT: "Replace the Whole Thing"

Think of PUT like throwing away your old character sheet and replacing it with a brand-new sheet.

  • What it does: It completely overwrites an existing item with the new information you send.
  • The Catch: If you leave something off the new sheet, it gets erased!
  • Game example: You want to change Alex's hat to a "Green Cap". With PUT, you must send the entire profile:
    • Name: Alex
    • Level: 5
    • Hat: Green Cap
    • Shoes: Red Sneakers (If you only sent "Hat: Green Cap", the server might erase Alex's level and shoes because you didn't include them on the new sheet!)
  • Key idea: Even if you run a PUT request 10 times in a row, the character sheet stays exactly the same as what you sent. It completely replaces what was there.

3. PATCH: "Fix Just a Part of It"

Think of PATCH like putting a band-aid or a sticker on something. You only touch the part you want to fix.

  • What it does: It updates only specific fields without touching the rest of the information.
  • Game example: You just want to change Alex's shoes. With PATCH, you only send:
    • Shoes: Gold Boots
  • The server looks at Alex, leaves the Name, Level, and Hat completely alone, and simply swaps out the shoes.
  • Key idea: It is lightweight and great when you only want to change one small detail without having to re-send the whole profile.

Quick Summary

  • POST: Create a brand-new item. (e.g., Make a new character)
  • PUT: Replace an entire existing item from top to bottom. (e.g., Overwrite the whole character sheet)
  • PATCH: Update just a specific piece of an existing item. (e.g., Change only the shoes)

Does this character sheet analogy make sense, or would you like to see how the actual code/data looks when a website sends these requests?

Sources:

This session also includes:

Comments 0