Resource Routes - PUT vs PATCH

Flexible != Rigid REST API.

If you want flexible, GET and POST all the way home.

I have to disagree.

You are right to an extent that POST is "flexible" on its own, as you can do anything with it, but that doesn't mean it provides for a flexible API.

You'll need good API design skills (and design is hard) to produce a sane RESTful API, but it is the rigid simplicity that makes REST very flexible.
Shoe-horning everything into GET and POST is a common thing only because of how browsers and HTML forms work. You can get away with that when you only need a current version of your app to work, but that is a luxury that you don't have when building APIs and it turns into a maintenance hell.

Read up on what "idempotency" means and you should know what I mean.

I'm pretty sure most of the APIs I've used were designed by either idiots or computer scientists that are so advanced they can no longer speak to other humans.

I did look up "idempotency", and it seems like something that I already expect for certain requests.

I'd like to see some examples of these sane RESTful APIs you speak of. Do you have any favorites?

Expert Website Development - Temecula, CA
Community Auth For CodeIgniter 3