Should I use PATCH or PUT in my REST API?

by

The PATCH method is the correct choice here as you’re updating an existing resource – the group ID. PUT should only be used if you’re replacing a resource in its entirety.

Further information on partial resource modification is available in RFC 5789. Specifically, the PUT method is described as follows:

Several applications extending the Hypertext Transfer Protocol
(HTTP) require a feature to do partial resource modification. The
existing HTTP PUT method only allows a complete replacement of a
document. This proposal adds a new HTTP method, PATCH, to modify an
existing HTTP resource.

More Related Contents:

  1. What is the difference between PUT, POST and PATCH?
  2. Which HTTP methods match up to which CRUD methods?
  3. RESTful Alternatives to DELETE Request Body
  4. Payloads of HTTP Request Methods
  5. What is the difference between POST and PUT in HTTP?
  6. What is the difference between POST and GET? [duplicate]
  7. Is an entity body allowed for an HTTP DELETE request?
  8. REST HTTP status codes for failed validation or invalid duplicate
  9. Use of PUT vs PATCH methods in REST API real life scenarios
  10. URL matrix parameters vs. query parameters
  11. Which status code should I use for failed validations or invalid duplicates?
  12. Detecting the character encoding of an HTTP POST request
  13. Why does my web server software disallow PUT and DELETE requests?
  14. Proper REST response for empty table?
  15. Content-Length header with HEAD requests?
  16. HTTP status code for a partial successful request
  17. What is the difference between HTTP and REST?
  18. Doing a HTTP PUT from a browser
  19. REST response code for invalid data
  20. Custom HTTP Authorization Header
  21. REST, HTTP DELETE and parameters
  22. Can I stream a file upload to S3 without a content-length header?
  23. Is REST DELETE really idempotent?
  24. How can I deal with HTTP GET query string length limitations and still want to be RESTful?
  25. What is the proper HTTP response to send for requests that require SSL/TLS
  26. How to set a timeout on a http.request() in Node?
  27. HTTP status code for temporarily unavailable pages
  28. nginx upload client_max_body_size issue
  29. “Cannot GET /” with Connect on Node.js
  30. Console errors. Failed to load resource: net::ERR_INSECURE_RESPONSE

Leave a Comment