You can use "query parameters" for "filtering" in REST, it is a common approach. Keep in mind that REST is a "architectural style", i.e., a set of principles that leave some room for interpretation. In your case I would say you could create something like this:
- query all products in stock:
GET /api/products?instock=true
- query products with only 1 left:
GET /api/products?countinstock=1
Where "instock" and "countinstock" are "query parameters", which you use in your REST API implementation as filters to query you DB.
This approach is commonly accepted in RESTful designs, namely you still have the "resource" (products) on which you perform a GET action/verb, the only extra part is the "query parameters" used to filter and constraint the "action" upon the "resources. See some further discussions in this topic (and supporting the user of "query parameters") here: