Design the GET Endpoint for Listing Products

One of the main operations of any API is to provide a way for the client to fetch all the available collections related to a resource. In our case, the resource is the product and the collection is the list of all products with their details. In HTTP, this is done via the GET method.

Before getting into the details of the endpoint, we need to keep the following details of the GET method in mind so that the API follows the HTTP specification:

• GET can only be used to retrieve data.
• A GET request has to be idempotent, i.e., the effect of multiple GET requests should be the same as a single GET request. For example, multiple GET calls with the same product ID should retrieve the same product.
• GET shouldn’t modify the resource associated with the request, i.e., a GET request shouldn’t make a change to the resource as a result of the call.
• A GET request can be cached either on the server side or the client side since the GET request identifies a resource.
• A GET request can be bookmarked by the client since it’s associated with a