The most commonly used HTTP verbs POST, GET, PUT, DELETE are similar to CRUD(Create, Read, Update and Delete) operations in database. We specify these HTTP verbs in the capital case.So, the below is the comparison between them.create--POST read -- GET update--PUT delete --DELETE

PATCH: Submits a partial modification to a resource. If you only need to update one field for the resource, you may want to use the PATCH methodThe POST verb is mostly utilized to create new resources. In particular, it's used to create subordinate resources. That is, subordinate to some other (e.g. parent) resource.On successful creation, return HTTP status 201, returning a Location header with a link to the newly-created resource with the 201 HTTP statusPUT is most-often utilized for update capabilities, PUT-ing to a known resource URI with the request body containing the newly-updated representation of the original resource.Checking with Fiddler or PostMan:- We can use the fiddler for checking the response. Open the fiddler and select the Compose tab . Specify the verb and url as shown below and click Execute to check the response.

PATCH: Submits a partial modification to a resource. If you only need to update one field for the resource, you may want to use the PATCH methodThe POST verb is mostly utilized to create new resources. In particular, it's used to create subordinate resources. That is, subordinate to some other (e.g. parent) resource.On successful creation, return HTTP status 201, returning a Location header with a link to the newly-created resource with the 201 HTTP statusPUT is most-often utilized for update capabilities, PUT-ing to a known resource URI with the request body containing the newly-updated representation of the original resource.Checking with Fiddler or PostMan:- We can use the fiddler for checking the response. Open the fiddler and select the Compose tab . Specify the verb and url as shown below and click Execute to check the response.

The most commonly used HTTP verbs POST, GET, PUT, DELETE are similar to CRUD(Create, Read, Update and Delete) operations in database. We specify these HTTP verbs in the capital case.So, the below is the comparison between them.create--POST read -- GET update--PUT delete --DELETE

POST: [HTTP.POST] can use when the client is sending data to the server and the server will decide the URI for the newly created resource. The POST method is used to request that the origin server accept the entity enclosed in the request as a new subordinate of the resource identified by the Request-URI in the Request-Line.PUT:[HTTP.PUT] can use when the client is sending data to the the server and the client is determining the URI for the newly created resource. The PUT method requests that the enclosed entity be stored under the supplied Request-URI. If the Request-URI refers to an already existing resource, the enclosed entity SHOULD be considered as a modified version of the one residing on the origin server. If the Request-URI does not point to an existing resource, and that URI is capable of being defined as a new resource by the requesting user agent, the origin server can create the resource with that URI.PATCH:[HTTP.PATCH] can use when the client is sending one or more changes to be applied by the the server. The PATCH method requests that a set of changes described in the request entity be applied to the resource identified by the Request-URI. The set of changes is represented in a format called a patch document.

POST: Helps to create new entity using few or more parameters. (Non Idempotent as it can work with few parameters and changes state at server) PUT: Is used for replacing entity if it exists (Idempotent) PATCH: Is used for updating entity if it exists

POST : URL creates a child resource at a server defined URL. PUT : URL creates/replaces the resource in its entirety at the client defined URL. PATCH : URL updates part of the resource at that client defined URL.The HTTP methods POST and PUT aren't the HTTP equivalent of the CRUD's create and update. They both serve a different purpose. It's quite possible, valid and even preferred in some occasions, to use PUT to create resources, or use POST to update resources.Use PUT when you can update a resource completely through a specific resource. For instance, if you know that an article resides at http://example.org/article/1234, you can PUT a new resource representation of this article directly through a PUT on this URL.If you do not know the actual resource location, for instance, when you add a new article, but do not have any idea where to store it, you can POST it to an URL, and let the server decide the actual URL.The HTTP methods PATCH can be used to update partial resources. For instance, when you only need to update one field of the resource, PUTting a complete resource representation might be cumbersome and utilizes more bandwidthAlso, the PUT method is idempotent. PUTting the same data multiple times to the same resource, should not result in different resources, while POSTing to the same resource can result in the creation of multiple resources.

PUT => If user can update all or just a portion of the record, use PUT (user controls what gets updated)PUT /users/123/email [email protected] PATCH => If user can only update a partial record, say just an email address (application controls what can be updated), use PATCH.PATCH /users/123 [description of changes]

@ raj kumar,I see your same answer 3 times, please delete 2

The most commonly used HTTP verbs POST, GET, PUT, DELETE are similar to CRUD(Create, Read, Update and Delete) operations in database. We specify these HTTP verbs in the capital case.So, the below is the comparison between them.create--POST read -- GET update--PUT delete --DELETE