Ask HN: At this point, are PUT and PATCH helpful?
2 by seph-reed | 6 comments on Hacker News.
I'm designing an API, and trying to place PUT and PATCH into my design ideology. In my experience, most APIs stick to GET and POST almost exclusively. And AFAICT, PUT and PATCH don't really add much that POST doesn't have. In fact, I kind of prefer the idea of having the url tell me what's going on explicitly rather than trying to infer from the request type. For example: - to create: `POST user` - to update: `POST user/12354` vs - to create: `POST user/` - to update: `PATCH user/` -------- I'm working alone on this project, otherwise I'd ask a coworker, but what do you guys think? What feels intuitive and clear to you?