Welcome to the Lidia Commerce Developer Portal

Lidia Commerce Developer Portal is a technical documentation hub designed for teams that want to develop integrations with Lidia products and services. Through this portal, you can review PIM APIs, Commerce Engine services, endpoint details, and real integration flows.

The documentation helps you understand what the APIs are used for, choose the right services, and start the integration process faster.

Documentation Structure

The Developer Portal presents the information you need during the integration process under three main sections.

Guides

Explains the general usage logic of the APIs, the distinction between PIM and Commerce Engine, the authentication structure, and common standards.

API Reference

Includes endpoint-based technical details. Request bodies, response models, HTTP methods, parameters, and sample requests are covered in this section.

Explore →

Recipes

Explains real integration scenarios step by step. Shows which API should be used and in what order.

Explore →

PIM

PIM is a Product Information Management structure used to configure, enrich, and manage product information from a single central point. Basic product information, category trees, brand relationships, technical attributes, variant structures, images, documents, and feed data are managed centrally within PIM.

With PIM, product data is kept more organized, up to date, and consistent. Product content can be used by different systems, sales channels, and integration structures through the same reliable data model.

View PIM documentation →

Product Data Data Enrichment Categories Brands Attributes Variants Assets Feeds

Commerce Engine

Commerce Engine consists of headless commerce services that manage sales operations. It enables commercial processes to be managed via APIs through services such as Metadata, Inventory, Order, Delivery, Identity, Content, and Notification.

Identity Metadata Order Inventory Delivery Collector Content Marketing Social Case Notification Organization Document

The Role of PIM and Commerce Engine in the Ecosystem

In the Lidia Commerce ecosystem, PIM and Commerce Engine are positioned in different layers. PIM is a SaaS-based Product Information Management solution that enables product information to be managed centrally. Commerce Engine is the headless commerce engine that works behind sales operations and manages processes such as inventory, pricing, orders, delivery, and similar operations through API-based services.

This section is prepared to explain the role of PIM in product data management and how Commerce Engine is positioned in the ecosystem with its operational commerce services.

What is it?

PIM It is a Product Information Management structure. It collects, classifies, enriches, and manages product information within a centralized data model. Product content, technical attributes, category/brand relationships, variant structures, images, documents, and feed information are handled within the scope of PIM.

View PIM documentation →

Commerce Engine It is a headless commerce service layer that manages e-commerce operations through APIs. Sales, inventory, order, delivery, and identity processes run through these services.

What does it do?

PIM It enables product data to be created, edited, enriched, and managed centrally. Product descriptions, technical attributes, category mappings, brand information, variants, images, and documents are managed under a single structure.

The main purpose of PIM is to prevent product information from being kept in scattered sources and to turn product data into a reliable, up-to-date, and consistent source.

Commerce Engine It manages the commercial operations of the product. Inventory, pricing, order, delivery, user, content, and notification processes are carried out through the relevant services.

How is it integrated?

PIM PIM APIs are used to create, query, update, or transfer product data to external systems. Integration is generally structured around product, category, brand, attribute, image, document, and feed data.

Commerce Engine The relevant service API is used depending on the integration need. For example, Inventory services are preferred for inventory and pricing, Metadata for reference data, and Order services for order processes.

Does it have an interface?

PIM It can be used together with a management interface where product information can be managed. APIs provide programmatic access to the product data managed in this interface.

Commerce Engine It has a headless structure. It does not provide a user interface; web, mobile, or different sales channels communicate with these services through APIs.

Authentication

PIM Client ID and AppKey information are used in PIM API requests.

Commerce Engine Authorization is performed with a Bearer token in Commerce Engine services.

Summary: PIM is the SaaS solution where product information is managed centrally and consistently. Commerce Engine is the service engine that makes this product information usable in commerce operations.