I'll direct you to the title of the post to which this comment is associated.
>> REST APIs must be hypertext-driven
> I am getting frustrated by the number of people calling any HTTP-based interface a REST API.
Now maybe I missed all the hypertext in postgrest, but given all of its documentation obviously fails the criteria of
> A REST API must not define fixed resource names or hierarchies (an obvious coupling of client and server).
I don't see how it could be in any way REST.
> Also, we've had Roy Fielding giving feedback[2] on an issue before.
That is feedback on an issue of HTTP implementation and compliance, it has nothing to do with REST.
Now look I really don't mind APIs being good HTTP citizens and having nothing to do with hypermedia, and that REST is an interesting idea doesn't mean it's a good idea (at least for programmatic APIs).
But it's like people saw a picture of a baby in a bath, went "well I don't need the pink thing in the middle but I'd sure like to wash up a bit", and when others point out they're carrying around a jug of soapy water which they insist is a baby called Fred those others get called "Baby purists"[-1].