> For the complete documentation index, see [llms.txt](https://help.citrusad.com/retail-media-interface/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.citrusad.com/retail-media-interface/integration/sk/data-api/catalog-products-2/syncing-catalog-via-api.md).

# Synchronizácia katalógu prostredníctvom API

Na synchronizáciu produktov potrebujete `catalogId` do ktorého budete dáta odosielať. Vo väčšine integrácií ho vo vašom mene vytvorí váš Technical Account Manager. Po vytvorení katalógu ho váš Technical Account Manager musí zviditeľniť vo vašom Epsilon Retail Media portáli.

## Kontext vytvorenia katalógu

Nižšie je uvedený príklad kontextu pre vytvorenie katalógu:

```http
POST $BASE_URL/v1/catalogs HTTP/1.1
accept: application/json
content-type: application/json
Authorization: Basic <API_KEY>
{
    "catalogs": [
        {
            "name": "Retailer A"
        }
    ]
}
```

V prípade úspechu sa vráti nasledujúci objekt:

```json
{
    "catalogs": [
        {
            "teamId": "9f48572c-0a5b-4997-9a0e-ed74f4d32dc6",
            "name": "Retailer A",
            "id": "216af452-d219-4807-b8ca-578bba446541"
        }
    ]
}
```

{% hint style="danger" %}
️

Po úspešnom vrátení objektu dostanete `id` pre váš nový katalóg. Ak rovnakú požiadavku odoslete znova, dostanete nové `id`, čím sa vytvoria dva katalógy.
{% endhint %}

{% hint style="info" %}
Budete potrebovať toto `id` na synchronizáciu produktov.
{% endhint %}

## Vytvorenie viacerých katalógov

Ak vytvárate viacero katalógov, môžete ich zoradiť do sekvencie až 100 v jednej požiadavke. Nižšie je uvedený príklad kontextu pre vytvorenie dvoch katalógov:

```http
POST $BASE_URL/v1/catalogs HTTP/1.1
accept: application/json
content-type: application/json
Authorization: Basic <API_KEY>
{
    "catalogs": [
        {
            "name": "Retailer A"
        },
        {
            "name": "Retailer B"
        }
    ]
}
```

V prípade úspechu sa vráti nasledujúci objekt (každý katalóg bude mať svoje vlastné individuálne `id`):

```json
{
    "catalogs": [
        {
            "teamId": "9f48572c-0a5b-4997-9a0e-ed74f4d32dc6",
            "name": "Retailer A",
            "id": "216af452-d219-4807-b8ca-578bba446541"
        },
        {
            "teamId": "9f48572c-0a5b-4997-9a0e-ed74f4d32dc6",
            "name": "Retailer B",
            "id": "75047339-65f5-41b8-8f2c-e76b04716cd4"
        }
    ]
}
```

{% hint style="warning" %}
Katalóg je po vytvorení predvolene skrytý. Kontaktujte svojho Technical Account Managera, aby bol váš katalóg viditeľný vo vašom namespace.
{% endhint %}


---

# 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://help.citrusad.com/retail-media-interface/integration/sk/data-api/catalog-products-2/syncing-catalog-via-api.md?ask=<question>&goal=<endgoal>
```

`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.