PUT/PATCH REST APIs - All you need to know about why and where to use Put vs Patch

We are very glad to start the REST APIs made easy course with the very first video on fundamentals of REST APIs, HTTP Methods, taxonomy around REST APIs etc. We hope that you get some value out of this course and these concepts help you thrive in your jobs, interviews and help you become better software engineers every day. Here are few links that you might want to refer before or during the course:

More on the topic:

------------------------------------------------------------------
Recommendations
------------------------------------------------------------------
Our full courses on youtube:

Some paid courses that we recommend:

------------------------------------------------------------------
About Us
------------------------------------------------------------------
Created and Instructed by:
Yogita Sharma

Post-production(editing, thumbnail etc) managed by:
CiKi

Colors and design by:
Naini Todi

Both Arpit and Yogita are software engineers and want to help other software engineers become better by providing high quality and well researched content by adding their creativity and teaching twist.

------------------------------------------------------------------
Join Us
------------------------------------------------------------------
Hangout with sudoCode:

For business:

[Rakeshkumar-twez]

short and simple explanation of PATCH and PUT. we are not using PATCH in our product as the records are not so heavy, Able to manage changes with PUT itself. But found the use case of PATCH very informative, thanks.

[a_lone_wonderer]

Damn, so many videos later, this video was successful in explaining the difference in PUT and PATCH in a concise and crisp way, specifically the upsert part, you made my day, keep up the good work...

[saumitrasaxena]

audio is very low.. in the advertisement I can hear properly but when Yogita is talking it's very low. I managed to listen with full concentration... good content.

[avigarg]

This is what we call precise and short intro. Thanku so much mam for sharing the knowledge

[MrMLBson]

This was flawlessly explained. You should be proud, very well done and very informative. Thank you.

[Luca-reve]

very useful video, always had trouble to understanding the difference, short and clear video, straight to the point

[darshanpandya]

Thank You ma'am for the brief introduction...

[sumanthkeith]

I have never got an opportunity to use patch request. Thanks for the informative video.
Please make videos on java design patterns. Easy way to understand and remeber 😋

[Rohitkumar-huqs]

Thanks a lot, Yogita. Excellent content and very simply put together. Please keep up the great work 👍

[halconElectrico]

Finally the concept is crystal clear. Thank you Yogita

[vigneshravichandran]

Just started watching ur videos.., the flow in which u explain is nice

[saranyajothi]

Very good and clear explanation about put and patch.... Thank you so much for such a wonderful video..if possible kindly upload videos on rest assured..

[xotic]

bohut kuch tumse sikhne ko mil raaha he yogita di

[nagendernaroju]

This is an excellent video, very much care has been taken while preparing the content at perfection.

[saumitrasaxena]

Hi Yogita, You said that in Put Request we mention id in the request body and not in path param, but later in 5:32 you are saying we will get 404 if we put wrong id in path param. This is a contradiction as in put request we are not supposed to put id in path param whether correct or incorrect.

[shortsbyparul]

The best video that I have ever come across. Spot On and to the point. Thanks a ton :)

[fatimaiqra]

thanks a lot ma'am, u have explained very nicely!

[Mohamed_developer_]

U r a good teacher...can u post a separate video about mongodb query like insert, delete,update, retrieve and some other queries...and types of errors when we use this queries....it will be helpful us....can u....?

[devendrawangikar]

As you have explained different methods and Idempotency behaviour very well, Can you please also explain behaviour and best practices around concurrent requests with method as PUT, PATCH ? Thank you.

[TalesByYogi]

at 8:20 you said that put request is idempotent as the state of the server is not going to change, no matter how many times you make the request. But first time obviously it'll update the information and second time onwards, there will be no change.

So doesnt that makes it non-idempotent?

Please clarify.