> For the complete documentation index, see [llms.txt](https://integrations.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://integrations.impact.com/brand-api-reference/reference/catalogs.md). # Catalogs *Product catalogs* are data feeds that hold a list of your products and their metadata, like an image of them or their current price. Product catalogs are commonly created via an e-commerce or shopping cart solution, which are then imported to impact.com. While you cannot create or delete a catalog directly via the API, you can use it to automate several key management tasks. The API enables you to programmatically update a catalog's settings, upload a file to populate it, and manage the individual items within it. Product catalogs are used to show your partners what products you sell and supply them with information on those products. For all other management functions, including creating and deleting catalogs, see the [Product Catalogs](https://app.impact.com/secure/advertiser/engage/ads/productcatalogs/manage-ads-product-catalog-flow.ihtml) screen in the impact.com web app. --- # 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://integrations.impact.com/brand-api-reference/reference/catalogs.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.