/catalogues

This endpoint of the Lengow API allows you to manage your product catalogues without relying on manual imports or UI-based updates. It enables you to:

• Retrieve your existing catalogues and additional sources

• Read catalogue structures and attributes

• List, retrieve, create, update, and delete a single product or a group of products

• Keep your product data continuously synchronized from your systems (PIM, ERP, custom tools)

Supported API features

Key Concepts

- catalogue_id

API requests must target a specific catalogue using its "catalogue_id".

• List catalogues is typically the first endpoint to call as it returns a list of all the main catalogues and additional sources available on the account. It includes the "catalogue_id" for each one, which is used for all subsequent requests. 
• Get catalogue uses the "catalogue_id" to return the metadata of a main catalogue or additional source (such as its name, status, product_id_key, etc.).

Example response for GET /catalogues/{catalogue_id} :

{
    "catalogue_id": 95000,
    "name": "Main Catalogue",
    "status": "enabled",
    "product_id_key": "id_product",
    "created_at": "2024-09-11T10:42:28.661555Z",
    "updated_at": "2025-11-06T13:57:48.078126Z",
    "indexed_at": "2025-11-06T13:57:49.571801Z",
    "source": "link",
    "products_count": 2134
}

- product_id_key

All product-related API operations rely on the "product_id_key" (shown in the response above).

The "product_id_key" is defined in your catalogue settings in Lengow and identifies the field that contains the unique product ID. 
For more information, see Initial product attributes mapping

When calling a product endpoint (for example, Get product), you must provide the product ID value stored in the catalogue field defined as the product_id_key.
 

API endpoints overview