What is the difference between a PUT and a PATCH request?

The PUT HTTP verb is used to create or replace the resource under a specific URI completely. In case the resource under a particular URI already exists, it will be completely overwritten by the payload that you send. In case the resource under the particular URI does not exist, the resource will be created.

Practically speaking PUT always almost means replacing an existing resource though because most APIs will not allow the client to choose the URI of a particular resource that does not exist.

In contrast, the PATCH HTTP verb describes what changes should be applied to an existing resource to create a new version. In this case, only individual fields are modified to create a newer and updated version of the resource.

In some sense you could argue that PATCH is less invasive than PUT in the sense that only individual fields are updated whereas with PUT you replace the resource completely with a new state.

In the wild, you will oftentimes find APIs where the HTTP verbs are not properly mapped. I.e. you might find a PUT endpoint that only replaces individual fields of a resource.

[jgoebel]

What do you think about this video?
Let me know in the comments below

[yohananmiteo]

This is the explanation I was looking for since a long time… Thanks a lot

[MnAino]

I've been following up some tutorials from your Chanel, and OMG! The best practices and concise information are amazing! Hope you are doing well, kind of miss you already.

[abhiramsatpute]

Amazing! My understanding from this video is that PUT is analogous to object-like storage in S3, and also it comes with high security risk of data manipulation

[rijuroy]

Very clearly described the difference. Thanks a ton.

[simonIsDev]

It's so very useful for me, thanks you very much <3

[paulwong]

Great video. Thanks! My summary:
PUT - Creates or replaces entirely
PATCH - Updates fields

[hetalchavan]

I am a tad bit confused about following statements:
1. Put can be used to create a resource which doesn't exist
2. While trying to replace a resource which doesn't exist, an error will be thrown.
Can you please clarify the above?

[astartesidon]

dats why i always use patch when updating

[georgesmith]

Yes, I noticed times and again that whoever wrote the specification did not really go over them logically and make sure there was no overlap. The explanation here was good. The reality though is staggering as developers who never read the spec "REST-ful", or should I say REST-like code. Of course, I can't blame them - they are constantly assigned 2.5 their possible workload ALL the time. So who has time to read the spec!? The managers just wants them to close the tickets, so the report looks good.