> For the complete documentation index, see [llms.txt](https://docs.evitalrx.in/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.evitalrx.in/api-for-product-catalogue/introduction.md). # Introduction This bundle provides APIs for managing and retrieving product information, including searching for medicines, viewing product details, exploring categories, and requesting products. It helps to smooth the product catalog management. **Here is the Postman Collection of APIs** {% file src="/files/GajXpUODpaBcAjmcfivO" %} ## Sequence Diagram

This flowchart illustrates the process of interacting with a product catalog API bundle. The user selects an action (such as searching for products, viewing product details, or browsing categories), and the system calls the corresponding API to fetch the relevant data. Once the API responds, the system returns the results to the user. This flow ensures efficient product catalog management by handling different user requests like searching, viewing, or requesting products.

**Watch a video.** {% embed url="" %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.evitalrx.in/api-for-product-catalogue/introduction.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.