> For the complete documentation index, see [llms.txt](https://crownpeak.gitbook.io/product-discovery/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://crownpeak.gitbook.io/product-discovery/sending-and-managing-product-data/what-is-the-items-api/working-with-items/item-catalog.md).

# Item Catalog

## Definition

Registering a catalog creates a version. Only one catalog version can be activated. The activated catalog version is set to "*active*" and will be used by the search and recommendation.\
Only 2 catalogs at the same time are managed by the API. If this limit is reached, one catalogue must be deleted to create another one.

Having different versions of the catalog allows preparing a version to be activated, or to go back and activate an old version.

## Structure

| **Name**             | type    | **Description**                              |
| -------------------- | ------- | -------------------------------------------- |
| tenant               | string  | Tenant of the account                        |
| environment          | string  | Environment to use                           |
| version              | integer | Automatically created                        |
| name                 | string  | Optional catalog name                        |
| state                |         | List of states: INACTIVE, ACTIVATING, ACTIVE |
| catalogItemSchemas   | list    | List of itemSchema used in the catalog       |
| catalogCategoryTrees | list    | List of categoryTreed used in the catalog    |

The *catalog\_item\_schemas and catalogCategoryTrees* fields are a list of objects containing the name and version of the item schema/category tree and should look like this:

```javascript
[
    {
        "name": "product",
        "version": 2
    }
]
```


---

# 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:

```
GET https://crownpeak.gitbook.io/product-discovery/sending-and-managing-product-data/what-is-the-items-api/working-with-items/item-catalog.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.