Postgrest deviates from some REST URL conventions that REST users are familiar with.  As an example, one very common convention gives each item a distinct path with the &#x27;id&#x27; (the primary key of some table, typically) as the last path element: &#x2F;some_path&#x2F;123.  Notice that the &#x27;key&#x27; column name is implied and simple (not compound).<p>Postgrest does not adopt this convention.  This decision is not arbitrary, however.  Postgrest is conceptually a function that computes a REST API for a PostgreSQL database, and tables in a PostgreSQL can (for better or worse) have compound primary keys, which do not map well to a simple URL path.  So Postgrest uses a more general URL syntax.  The equivalent of the above is: &#x2F;some_path?id=eq.123.<p>Postgrest represents some novel thinking about the use of certain HTTP verbs as well.  A lot of this is discussed in the Postrest introduction video here: <a href="http:&#x2F;&#x2F;postgrest.com&#x2F;" rel="nofollow">http:&#x2F;&#x2F;postgrest.com&#x2F;</a>