Другие разделы API Lamoda

Date: 2025-02-10 Subtask: 2-12 - Document all other API sections Status: ✅ COMPLETED

Overview

This document provides detailed documentation for all remaining API sections in the Lamoda marketplace that were not covered in previous endpoint documentation files. These sections include:

1. Addresses (Адреса) - Address lookup and validation
2. Delivery (Доставка) - Delivery methods and information
3. Pickup Points (Пункты выдачи) - Pickup point locations and details
4. Partner Pickups (Забор товара) - Partner pickup point management
5. Gift Certificates (Подарочные сертификаты) - Gift certificate generation and management
6. Labels (Этикетки) - Shipping label generation
7. Notifications (Уведомления) - Order and shipment status notifications
8. Container/Barcodes - Package and container information
9. Dictionaries (Справочники) - Reference data and metadata
10. Attributes (Атрибуты) - Product attributes management
11. Categories (Категории) - Product categories and ERP categories
12. Questions (Вопросы покупателей) - Customer questions and answers
13. Feedback (Обратная связь) - Customer feedback management

---

1. Addresses (Адреса)

API for address lookup, validation, and autocomplete functionality using KLADR codes.

1.1 Get City Suggestions

Endpoint: GET /api/v1/addresses/city

Description: Получить предложения по городам (Get city suggestions)

Request Parameters:

Parameter	Type	Required	Description	Example
name	string	Yes	Название города (City name)	"Москва"

Response Schema (200 OK):

{
  "code": 200,
  "data": [
    {
      "id": "7700000000000",
      "text": "Москва",
      "text_extended": "г Москва",
      "zipcode": "101000"
    }
  ]
}

Field Descriptions:

• id (string): KLADR code of the city
• text (string): City name
• text_extended (string): Extended city name with type
• zipcode (string): Postal code

1.2 Get Street Suggestions

Endpoint: GET /api/v1/addresses/street

Description: Получить список улиц (Get street list)

Request Parameters:

Parameter	Type	Required	Description	Example
name	string	Yes	Название улицы (Street name)	"Тверская"
parentId	string	No	КЛАДР-код населенного пункта (KLADR code of locality)	"7700000000000"

Response Schema (200 OK):

{
  "code": 200,
  "data": [
    {
      "id": "77000000000711300",
      "text": "ул. 1-я Тверская-Ямская",
      "zipcode": "125047"
    }
  ]
}

Field Descriptions:

• id (string): KLADR code of the street
• text (string): Street name
• zipcode (string): Postal code

1.3 Get Building Suggestions

Endpoint: GET /api/v1/addresses/building

Description: Получить список зданий (Get building list)

Request Parameters:

Parameter	Type	Required	Description	Example
name	string	Yes	Номер здания (Building number)	"1"
parentId	string	No	КЛАДР-код улицы (KLADR code of street)	"77000000000287900"

Response Schema (200 OK):

{
  "code": 200,
  "data": [
    {
      "id": "770000000002879000033",
      "text": "20/1",
      "zipcode": "125047",
      "coordinates": {
        "latitude": "55.724809",
        "longitude": "35.724809"
      }
    }
  ]
}

Field Descriptions:

• id (string): KLADR code of the building
• text (string): Building number
• zipcode (string): Postal code
• coordinates (object): Geographic coordinates
  • latitude (number): Latitude coordinate
  • longitude (number): Longitude coordinate

---

2. Delivery (Доставка)

API for retrieving available delivery methods, intervals, and delivery information.

2.1 Get Available Delivery Types

Endpoint: GET /api/v1/delivery_info

Description: Получить доступные способы доставки (Get available delivery methods)

Request Parameters:

Parameter	Type	Required	Description	Example
aoid	string	Yes	КЛАДР-код объекта (KLADR code, preferably city)	"7700000000000"

Response Schema (200 OK):

[
  {
    "methodTypeCode": "delivery_service",
    "methodTypeName": "Курьерская доставка",
    "serviceLevelTypeCode": "plus",
    "serviceLevelTypeName": "С примеркой",
    "checkoutMethodCode": "lamoda",
    "checkoutMethodName": "Курьерская доставка Lamoda Express"
  }
]

2.2 Get Delivery Methods and Intervals

Endpoint: GET /api/v1/delivery_methods

Description: Получить методы и интервалы доставки (Get delivery methods and intervals)

Request Parameters:

Parameter	Type	Required	Description	Example
address_object_id	string	Yes	КЛАДР-код объекта (KLADR code, preferably building)	"770000000001707000021"
item_count	integer	No	Количество товаров в заказе (Number of items)	1
cart_amount	number	No	Общая сумма заказа (Total cart amount in rubles)	1499.0
method_type_codes[]	array	No	Код типа доставки (Delivery type codes: delivery_service, post)	["delivery_service"]
is_liquid	boolean	No	Наличие жидкости в заказе (Contains liquids)	false

Response Schema (200 OK):

[
  {
    "methodTypeCode": "delivery_service",
    "methodTypeName": "Курьерская доставка",
    "serviceLevelTypeCode": "plus",
    "serviceLevelTypeName": "С примеркой",
    "serviceLevelTypeDescription": "Доставка в выбранный час",
    "checkoutMethodCode": "lamoda",
    "checkoutMethodName": "Курьерская доставка Lamoda Express",
    "checkoutMethodCategoryName": "Методы LME (плюс + эконом)",
    "checkoutMethodCheckoutDescription": "Доставка бесплатная, вне зависимости от суммы покупки",
    "checkoutMethodHasHorizon": true,
    "checkoutMethodHasIntervals": true,
    "checkoutMethodIsClientNameRequired": false,
    "checkoutMethodDeliveryPrice": 800,
    "checkoutMethodFreeDeliveryNetThreshold": 2000,
    "isRejectionAllowed": true,
    "isTryonAllowed": true,
    "deliveryDateMin": "2018-04-11",
    "deliveryDateMax": "2018-04-15",
    "dayDate": "2018-04-11",
    "intervalId": 561502110,
    "intervalStart": "13:59",
    "intervalEnd": "23:59"
  }
]

Field Descriptions:

• methodTypeCode (string): Delivery type code (delivery_service, post, pickup, store)
• methodTypeName (string): Delivery type name
• serviceLevelTypeCode (string): Service level code (plus, economy, standard)
• serviceLevelTypeName (string): Service level name
• checkoutMethodCode (string): Checkout method code
• checkoutMethodName (string): Checkout method name
• checkoutMethodDeliveryPrice (number): Delivery price in rubles
• checkoutMethodFreeDeliveryNetThreshold (number): Free delivery threshold in rubles
• deliveryDateMin (string): Minimum delivery date (YYYY-MM-DD)
• deliveryDateMax (string): Maximum delivery date (YYYY-MM-DD)
• intervalId (integer): Delivery interval ID
• intervalStart (string): Interval start time (HH:mm)
• intervalEnd (string): Interval end time (HH:mm)

2.3 Add Delivery Information

Endpoint: POST /api/v1/delivery_info/{orderNr}

Description: Добавить информацию о доставке (Add delivery information)

Path Parameters:

Parameter	Type	Required	Description
orderNr	string	Yes	Номер заказа Lamoda (Lamoda order number)

Query Parameters:

Parameter	Type	Required	Description	Example
tracking_number	string	No	Трек-номер для отслеживания (Tracking number)	"ED-121"
tracking_url	string	No	Ссылка для отслеживания (Tracking URL)	"https://expressdelivery.ru/ED-121"
courier_service_name	string	No	Наименование курьерской службы (Courier service name)	"ExpressDelivery"
courier_service_site_url	string	No	Ссылка на сайт курьерской службы (Courier service site URL)	"https://expressdelivery.ru"

Response (201 Created): Empty response body

---

3. Pickup Points (Пункты выдачи)

API for retrieving pickup point locations and details.

3.1 Get Pickup Points List

Endpoint: GET /api/v1/pickup_points

Description: Получить список пунктов самовывоза (Get pickup points list)

Request Parameters:

Parameter	Type	Required	Description	Example
aoid	string	Yes	Идентификатор адреса доставки (Delivery address ID - KLADR or GUI)	"7700000000000"
item_count	integer	Yes	Количество товаров в заказе (Number of items)	1
cart_amount	number	Yes	Общая сумма заказа в рублях (Total cart amount in rubles)	1499.0
method_type_codes[]	array	No	Код типа доставки (pickup, store)	["pickup"]
is_liquid	boolean	No	Наличие жидкости в заказе (Contains liquids)	false

Response Schema (200 OK):

{
  "pickupPoints": [
    {
      "id": 12345,
      "name": "ПВЗ Ламода ТЦ Океан",
      "address": "г. Москва, ул. Планетная, д. 6",
      "latitude": 55.724809,
      "longitude": 37.618489,
      "workTime": "Пн-Вс: 10:00-22:00",
      "deliveryDateMin": "2018-04-11",
      "deliveryDateMax": "2018-04-15",
      "hasIntervals": true,
      "intervals": [
        {
          "date": "2018-04-11",
          "intervals": [
            {
              "id": 563990086,
              "start": "10:00",
              "end": "12:00"
            }
          ]
        }
      ]
    }
  ]
}

3.2 Get Pickup Point Details

Endpoint: GET /api/v1/pickup_points/{id}

Description: Получить детальную информацию о пункте самовывоза (Get pickup point details)

Path Parameters:

Parameter	Type	Required	Description
id	integer	Yes	Цифровой идентификатор ПВЗ (Pickup point numeric ID)

Query Parameters: Same as /api/v1/pickup_points (aoid, item_count, cart_amount, method_type_codes[], is_liquid)

Response Schema (200 OK):

{
  "id": 12345,
  "name": "ПВЗ Ламода ТЦ Океан",
  "address": "г. Москва, ул. Планетная, д. 6",
  "latitude": 55.724809,
  "longitude": 37.618489,
  "workTime": "Пн-Вс: 10:00-22:00",
  "deliveryDateMin": "2018-04-11",
  "deliveryDateMax": "2018-04-15",
  "hasIntervals": true,
  "intervals": [
    {
      "date": "2018-04-11",
      "intervals": [
        {
          "id": 563990086,
          "start": "10:00",
          "end": "12:00"
        }
      ]
    }
  ]
}

Field Descriptions:

• id (integer): Pickup point ID
• name (string): Pickup point name
• address (string): Pickup point address
• latitude (number): Latitude coordinate
• longitude (number): Longitude coordinate
• workTime (string): Working hours
• deliveryDateMin (string): Minimum delivery date (YYYY-MM-DD)
• deliveryDateMax (string): Maximum delivery date (YYYY-MM-DD)
• hasIntervals (boolean): Whether delivery intervals are available
  • If true: Use intervals[].date and intervals[].intervals for specific dates and times
  • If false: Use deliveryDateMin and deliveryDateMax as approximate delivery dates

---

4. Partner Pickups (Забор товара)

API for managing partner pickup points (warehouse locations).

4.1 Create Partner Pickup Point

Endpoint: POST /api/v1/partner-pickups

Description: Добавить партнерский ПВЗ (Add partner pickup point)

Request Schema:

{
  "name": "My Warehouse",
  "address": "г. Москва, ул. Примерная, д. 1",
  "contactPerson": "Иван Иванов",
  "phone": "+79991234567",
  "warehouseCode": "WH001"
}

Response (201 Created): Returns created pickup point ID

4.2 Update Partner Pickup Point

Endpoint: PATCH /api/v1/partner-pickups

Description: Обновить информацию о ПВЗ (Update partner pickup point)

Request Schema: Same as POST /api/v1/partner-pickups

Response (201 OK): Returns updated pickup point ID

4.3 Get Partner Pickup Points

Endpoint: GET /api/v1/partner-pickups

Description: Получить список существующих ПВЗ (Get partner pickup points list)

Response Schema (200 OK):

{
  "pickupPoints": [
    {
      "id": "PP123",
      "name": "My Warehouse",
      "address": "г. Москва, ул. Примерная, д. 1",
      "contactPerson": "Иван Иванов",
      "phone": "+79991234567",
      "warehouseCode": "WH001",
      "isActive": true
    }
  ]
}

---

5. Gift Certificates (Подарочные сертификаты)

API for generating and managing gift certificates.

5.1 Get Gift Certificates List

Endpoint: GET /api/v1/gift-certificates

Description: Получить список сертификатов (Get gift certificates list)

Request Parameters:

Parameter	Type	Required	Description	Example
certificate_code	string	No	Код сертификата (Certificate code)	"GIFT123456"
date_from	string	No	Дата начала действия (Valid from date)	"2024-01-01"
date_to	string	No	Дата окончания действия (Valid to date)	"2024-12-31"
payment_status	string	No	Статус оплаты (Payment status)	"Paid"
processing_status	string	No	Статус сертификата (Processing status)	"Active"

Response Schema (200 OK):

[
  {
    "certificate_code": "GIFT123456",
    "nominal": 1000,
    "currency": "RUB",
    "date_create": "2024-01-01",
    "date_from": "2024-01-01",
    "date_to": "2024-12-31",
    "payment_status": "Paid",
    "processing_status": "Active"
  }
]

Field Descriptions:

• certificate_code (string): Unique certificate code
• nominal (number): Certificate nominal value
• currency (string): Currency code (RUB)
• date_create (string): Creation date (YYYY-MM-DD)
• date_from (string): Valid from date (YYYY-MM-DD)
• date_to (string): Valid to date (YYYY-MM-DD)
• payment_status (string): Payment status (Not paid, Paid)
• processing_status (string): Processing status (New, Active, Used, Expired)

5.2 Generate Gift Certificates

Endpoint: POST /api/v1/gift-certificates

Description: Генерация сертификатов (Generate gift certificates)

Request Schema:

{
  "nominal": 1000,
  "quantity": 10,
  "date_from": "2024-01-01",
  "date_to": "2024-12-31"
}

Request Parameters:

Parameter	Type	Required	Description	Example
nominal	number	Yes	Номинал сертификата (Certificate nominal value)	1000
quantity	integer	Yes	Количество сертификатов (Number of certificates)	10
date_from	string	Yes	Дата начала действия (Valid from)	"2024-01-01"
date_to	string	Yes	Дата окончания действия (Valid to)	"2024-12-31"

Response Schema (200 OK):

[
  {
    "certificate_code": "GIFT123456",
    "nominal": 1000,
    "payment_status": "Not paid",
    "processing_status": "New"
  }
]

Note: Generated certificates have status "New" and payment status "Not paid". Use POST /api/v1/gift-certificates/payments to mark them as paid.

5.3 Get Gift Certificate Balance

Endpoint: GET /api/v1/gift-certificates/balance

Description: Получить баланс (Get gift certificate balance)

Response Schema (200 OK):

{
  "balance": "50000.00"
}

Note: Balance is the sum of certificate nominals that can be marked as paid.

5.4 Mark Certificates as Paid

Endpoint: POST /api/v1/gift-certificates/payments

Description: Перевести сертификат в статус Paid (Mark certificates as paid)

Request Schema:

{
  "certificate_codes": ["GIFT123456", "GIFT123457"]
}

Request Parameters:

Parameter	Type	Required	Description
certificate_codes	array	Yes	Список кодов сертификатов (List of certificate codes)

Response Schema (200 OK):

[
  {
    "certificate_code": "GIFT123456",
    "payment_status": "Paid"
  },
  {
    "certificate_code": "GIFT123457",
    "payment_status": "Paid"
  }
]

Note: Certificates can only be marked as paid if the balance is sufficient. Only paid certificates can be used by customers.

---

6. Labels (Этикетки)

API for generating shipping labels.

6.1 Get Shipping Label

Endpoint: GET /api/v1/reports/label/stream

Description: Получить этикетки по заказу (Get shipping labels for order)

Request Parameters:

Parameter	Type	Required	Description	Example
orderNr	string	Yes	Номер заказа (Order number)	"RU123456-123456"
packBarcode	string	Yes	Уникальный номер посылки (Unique pack barcode)	"PACKDKY212"
multiPacks	boolean	Yes	Наличие нескольких посылок (Multiple packs in order)	false

Response Schema (200 OK):

Returns PDF file content (application/pdf)

Response Codes:

• 200 OK: Label generated successfully
• 400 Bad Request: Invalid parameters
• 500 Internal Server Error: Server error

---

7. Notifications (Уведомления)

API for resending order and shipment status notifications.

7.1 Resend Notifications

Endpoint: POST /api/v1/notifications/resend

Description: Переотправить уведомления о статусах заказов или товаров (Resend order/item status notifications)

Request Schema:

{
  "order_numbers": ["RU123456-123456", "RU123456-123457"]
}

Request Parameters:

Parameter	Type	Required	Description
order_numbers	array	Yes	Список номеров заказов (List of order numbers, max 100)

Response Schema (200 OK):

{
  "success": ["RU123456-123456"],
  "already_in_progress": ["RU123456-123457"]
}

Response Codes:

• 200 OK: Notifications accepted for resending
• 400 Bad Request: Invalid request
• 401 Unauthorized: Authentication error
• 429 Too Many Requests: Rate limit exceeded (notifications already in progress)
• 500 Internal Server Error: Server error

---

8. Container/Barcodes

API for retrieving package and container information.

8.1 Get Container Information

Endpoint: GET /api/v1/container/{barcode}

Description: Получить информацию о посылках в поставке (Get package/container information)

Path Parameters:

Parameter	Type	Required	Description	Example
barcode	string	Yes	Штрих-код посылки (Package barcode)	"PACKIX21328149885700100032"

Query Parameters:

Parameter	Type	Required	Description	Example
limit	integer	No	Количество значений на странице (Page size)	25
page	integer	No	Номер страницы (Page number)	1

Response Schema (200 OK):

{
  "page": 1,
  "limit": 25,
  "pages": 1,
  "total": 10,
  "_links": {
    "self": {
      "href": "/api/v1/container/PACKIX21328149885700100032?page=1"
    }
  },
  "_embedded": {
    "goods": [
      {
        "sku": "IX001XW016SJINM",
        "supplier_sku_id": "123456789",
        "datamatrix": "01043461007313420321vOc+U_eOPcF",
        "pack_barcode": "PACKIX21328149885700100032",
        "pallet_barcode": "PALIX213766403",
        "shipment_id": "IX213766497",
        "order_id": "61688940",
        "order_nr": "RU220109-992581",
        "order_status": "Shipped to WH",
        "created_at": "2022-01-14"
      }
    ]
  }
}

Field Descriptions:

• sku (string): Lamoda SKU
• supplier_sku_id (string): Partner SKU
• datamatrix (string): DataMatrix code (UIT)
• pack_barcode (string): Package barcode
• pallet_barcode (string): Pallet barcode
• shipment_id (string): Shipment ID
• order_id (string): Order ID
• order_nr (string): Order number
• order_status (string): Order status
• created_at (string): Creation date (YYYY-MM-DD)

---

9. Dictionaries (Справочники)

JSON-RPC API for retrieving reference data and metadata.

9.1 Get Dictionaries

Endpoint: POST /jsonrpc/v1/dictionaries.get

Description: Справочник аттрибутов пользователя (User attributes dictionary)

JSON-RPC Request:

{
  "jsonrpc": "2.0",
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "method": "v1.dictionaries.get",
  "params": {}
}

Response Schema:

{
  "jsonrpc": "2.0",
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "result": {
    "order_statuses": {
      "to_delivery": {
        "title": "Sent to delivery",
        "value": "to_delivery",
        "is_common": true
      }
    },
    "business_models": ["consignment", "fbo"],
    "partners": [
      {
        "code": "MX",
        "partner_id": 12345,
        "shop_name": "MyShop",
        "business_model": "consignment"
      }
    ],
    "countries": [
      {
        "code": "RU",
        "name": "Russia"
      }
    ],
    "item_statuses": ["new", "in_progress", "done"],
    "user": {
      "external_id": "e8fe22db-e41d-4fc4-a334-e087189c51a"
    }
  }
}

Field Descriptions:

• order_statuses (object): Order status dictionary
  • title (string): Status title
  • value (string): Status value
  • is_common (boolean): Whether status is common
• business_models (array): Available business models (consignment, fbo)
• partners (array): Partner information
  • code (string): Partner code
  • partner_id (integer): Partner ID
  • shop_name (string): Shop name
  • business_model (string): Business model
• countries (array): Available countries
  • code (string): Country code (RU, BY, KZ, UA)
  • name (string): Country name
• item_statuses (array): Available item statuses
• user (object): User information
  • external_id (string): External user ID

9.2 Get Axapta Categories

Endpoint: POST /jsonrpc/v1/nomenclatures-metadata.get-axapta-categories

Description: Список доступных категорий аксапты для партнера (Get Axapta categories)

JSON-RPC Request:

{
  "jsonrpc": "2.0",
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "method": "v1.nomenclatures.metadata.get-axapta-categories",
  "params": {
    "filter": []
  }
}

Response Schema:

{
  "jsonrpc": "2.0",
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "result": ["CLOTHES", "SHOES", "ACCESSORIES"]
}

9.3 Get Brands

Endpoint: POST /jsonrpc/v1/nomenclatures-metadata.get-brands

Description: Список доступных брендов для партнера (Get brands)

JSON-RPC Request:

{
  "jsonrpc": "2.0",
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "method": "v1.nomenclatures.metadata.get-brands",
  "params": {
    "filter": []
  }
}

Response Schema:

{
  "jsonrpc": "2.0",
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "result": [
    {
      "name": "Adidas"
    },
    {
      "name": "Nike"
    }
  ]
}

9.4 Get ERP Categories

Endpoint: POST /jsonrpc/v1/erp-categories.list

Description: Get ERP categories list

JSON-RPC Request:

{
  "jsonrpc": "2.0",
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "method": "v1.erp-categories.list",
  "params": {}
}

Response Schema:

{
  "jsonrpc": "2.0",
  "result": {
    "items": [
      {
        "rec_id": "5637156660",
        "name": "Clothing",
        "path": ["Apparel", "Clothing"],
        "allowed_for_nomenclature_template_generation": true,
        "translation_ru": "Одежда"
      }
    ]
  }
}

Field Descriptions:

• rec_id (string): Category record ID
• name (string): Category name
• path (array): Category path
• allowed_for_nomenclature_template_generation (boolean): Whether allowed for template generation
• translation_ru (string): Russian translation

---

10. Attributes (Атрибуты)

JSON-RPC API for managing product attributes.

10.1 Get Attributes by Category

Endpoint: POST /jsonrpc/v1/attributes.list

Description: Запрос на получение аттрибутов по указанной категории аксапты (Get attributes by Axapta category)

JSON-RPC Request:

{
  "jsonrpc": "2.0",
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "method": "v1.attributes.list",
  "params": {
    "rec_id": "5637156660"
  }
}

Request Parameters:

Parameter	Type	Required	Description
rec_id	string	Yes	ERP category record ID

Response Schema:

{
  "jsonrpc": "2.0",
  "result": {
    "items": [
      {
        "code": "brand",
        "label": "Бренд",
        "type": "string",
        "required": true,
        "comment": "Бренд товара",
        "allow_edit_for_seller": true
      }
    ]
  }
}

Field Descriptions:

• code (string): Attribute code
• label (string): Attribute label
• type (string): Attribute type (number, string, boolean, dictionary_entry, array_of_dictionary_entry, localized_string)
• required (boolean): Whether attribute is required
• comment (string): Attribute description
• allow_edit_for_seller (boolean): Whether seller can edit this attribute

10.2 Get Attributes by SKU

Endpoint: POST /jsonrpc/v1/attributes.sku.list

Description: Запрос на получение списка аттрибутов для указанного товара партнера (Get attributes by SKU)

JSON-RPC Request:

{
  "jsonrpc": "2.0",
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "method": "v1.attributes.sku.list",
  "params": {
    "sku": "SKU123"
  }
}

Request Parameters:

Parameter	Type	Required	Description
sku	string	Yes	Partner SKU

Response Schema:

{
  "jsonrpc": "2.0",
  "result": {
    "product": [
      {
        "code": "brand",
        "label": "Бренд",
        "value": "Nike"
      }
    ],
    "variation": {
      "size": [
        {
          "code": "size",
          "label": "Размер",
          "value": "M"
        }
      ]
    }
  }
}

10.3 Get Attribute Dictionaries

Endpoint: POST /jsonrpc/v1/attribute-dictionaries.list

Description: Get attribute dictionaries (lookup values)

JSON-RPC Request:

{
  "jsonrpc": "2.0",
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "method": "v1.attribute-dictionaries.list",
  "params": {
    "seller_id": "123",
    "dictionaries": ["brand", "color"]
  }
}

Request Parameters:

Parameter	Type	Required	Description
seller_id	string	No	Seller ID
dictionaries	array	No	List of dictionary names

Response Schema:

{
  "jsonrpc": "2.0",
  "result": {
    "brand": {
      "Nike": {
        "name": "Nike",
        "is_hidden": false
      }
    },
    "color": {
      "red": {
        "name": "Красный",
        "is_hidden": false
      }
    }
  }
}

10.4 Get Dictionary Mappings

Endpoint: POST /jsonrpc/v1/attributes-dictionaries-mappings.get

Description: Запрос на получение аттрибутов для указанной категории аксапты (Get category attribute mappings)

JSON-RPC Request:

{
  "jsonrpc": "2.0",
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "method": "v1.attributes.dictionaries.mapping",
  "params": {
    "rec_id": "5637156660"
  }
}

Response Schema:

{
  "jsonrpc": "2.0",
  "result": {
    "site_categories": [
      {
        "id": "cat123",
        "path": ["Clothing", "T-Shirts"],
        "name": "Футболки",
        "is_sport": false,
        "gender": "men"
      }
    ],
    "tn_ved": {
      "gender": ["men", "women"]
    },
    "title": {
      "room": ["Бельевой", "Домашний"]
    },
    "size_scale": {
      "size_value": ["S", "M", "L", "XL"],
      "gender": "men",
      "one_size_allowed": false
    },
    "brand_country_mapping": [
      {
        "brand_id": 123,
        "brand_name": "Nike",
        "is_sport": true,
        "countries_enabled": ["RU", "BY"]
      }
    ]
  }
}

---

11. Categories (Категории)

Categories are covered in the Dictionaries section (section 9). See:

• 9.2 Get Axapta Categories - Get Axapta categories
• 9.4 Get ERP Categories - Get ERP categories

---

12. Questions (Вопросы покупателей)

JSON-RPC API for managing customer questions about products.

12.1 Get Questions List

Endpoint: POST /jsonrpc/v1/questions.list

Description: Get questions list (Вопросы от клиентов)

JSON-RPC Request:

{
  "jsonrpc": "2.0",
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "method": "v1.questions.list",
  "params": {
    "seller_id": 123,
    "limit": 25,
    "page": 1,
    "id": ["550e8400-e29b-41d4-a716-446655440000"],
    "is_grouped": true,
    "sort": {
      "column": "date_create",
      "type": "desc"
    },
    "filter": {
      "status": ["new"],
      "answer_status": ["approved"],
      "answer_source": ["seller"]
    },
    "search": "блузка",
    "date_create_from": "2025-12-22T00:00:00+03:00",
    "date_create_to": "2025-12-31T23:59:59+03:00"
  }
}

Request Parameters:

Parameter	Type	Required	Description	Example
seller_id	integer	Yes	Идентификатор продавца (Seller ID)	123
limit	integer	Yes	Количество вопросов на странице (Page size, max 50)	25
page	integer	Yes	Номер страницы (Page number)	1
id	array	No	Список ID вопросов для фильтрации (Filter by question IDs)	["550e8400-..."]
is_grouped	boolean	No	Группировать по SKU товара (Group by SKU)	true
sort	object	No	Параметры сортировки (Sort parameters)	See below
filter	object	No	Фильтр по статусам (Filter by statuses)	See below
search	string	No	Поисковая строка (Search query)	"блузка"
date_create_from	string	No	Дата создания "от" (Created from)	"2025-12-22T00:00:00+03:00"
date_create_to	string	No	Дата создания "до" (Created to)	"2025-12-31T23:59:59+03:00"

Sort Parameters:

Parameter	Type	Description	Example
column	string	Column to sort by (only date_create supported)	"date_create"
type	string	Sort direction (asc, desc)	"desc"

Filter Parameters:

Parameter	Type	Description	Example
status	array	Filter by question status	["new", "in_progress", "answered", "rejected"]
answer_status	array	Filter by answer status	["approved", "rejected", "on_moderation"]
answer_source	array	Filter by answer source	["seller", "lamoda"]

Response Schema:

{
  "jsonrpc": "2.0",
  "result": {
    "data": [
      {
        "product": {
          "lamoda_parent_sku": "MP002XW0J7E6R",
          "lamoda_sku": "MP002XW0J7E6R660",
          "supplier_sku": "77122JSS-8",
          "name": "Тоник для лица",
          "brand": "New Balance",
          "images": {
            "default": [
              {
                "url": "https://pi.lmcdn.ru/product/MP002XW_v1.jpeg",
                "type": "main",
                "order": 1
              }
            ]
          }
        },
        "items": [
          {
            "id": "550e8400-e29b-41d4-a716-446655440000",
            "date_create": "2025-01-01T00:30:15",
            "date_answer_until": "2025-01-03T00:30:15",
            "username": "Мария",
            "text": "Текст вопроса",
            "can_answer": false,
            "answer_source": "seller",
            "status": "answered",
            "answers": [
              {
                "date_create": "2025-01-02T00:30:15",
                "text": "Текст ответа",
                "source": "seller",
                "status": "approved",
                "reject_reason": "Причина отклонения"
              }
            ]
          }
        ]
      }
    ],
    "pagination": {
      "limit": 25,
      "page": 1,
      "total": 120
    }
  }
}

Status Enums:

• Question Status (status):

  • new - Новый (New)
  • in_progress - В обработке (In progress)
  • answered - Отвечен (Answered)
  • rejected - Отклонен (Rejected)

• Answer Status (answer_status):

  • approved - Одобрен (Approved)
  • rejected - Отклонен (Rejected)
  • on_moderation - На модерации (On moderation)

• Answer Source (answer_source):

  • seller - Ответ продавца (Seller answer)
  • lamoda - Ответ Lamoda (Lamoda answer)

12.2 Answer Question

Endpoint: POST /jsonrpc/v1/questions.answer

Description: Answer on question (Ответить на вопрос)

JSON-RPC Request:

{
  "jsonrpc": "2.0",
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "method": "v1.questions.answer",
  "params": {
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "seller_id": 123,
    "text": "Текст ответа на вопрос"
  }
}

Request Parameters:

Parameter	Type	Required	Description	Example
id	string	Yes	ID вопроса (Question ID)	"550e8400-..."
seller_id	integer	Yes	Идентификатор продавца (Seller ID)	123
text	string	Yes	Текст ответа (Answer text, max 1000 chars)	"Текст ответа"

Response Schema:

{
  "jsonrpc": "2.0",
  "result": {}
}

---

13. Feedback (Обратная связь)

REST API for managing customer feedback and questions.

13.1 Get Feedback Questions

Endpoint: GET /v2/feedback/questions

Description: Метод на получение вопросов от клиентов (Get customer questions)

Base URL: https://public-api-seller.lamoda.ru/api

Request Parameters:

Parameter	Type	Required	Description	Example
sellerId	string	Yes	Идентификатор продавца (Seller ID)	"242541217"
page	integer	No	Номер страницы (Page number, default 1)	1
limit	integer	No	Количество на странице (Page size, max 1000, default 100)	100
sort	string	No	Сортировка (Sort: createdAt or -createdAt)	"createdAt"
createdFrom	string	No	Дата создания "от" (Created from, ISO 8601)	"2025-09-11T13:00:00Z"
createdTo	string	No	Дата создания "до" (Created to, ISO 8601)	"2025-09-12T13:00:00Z"
isGrouped	boolean	No	Группировать по товару (Group by product)	true
search	string	No	Поисковая строка (Search query, max 1000 chars)	"блузка"
status	array	No	Статус вопроса (Question status)	["NEW", "IN_PROGRESS"]
answerStatus	array	No	Статус ответа (Answer status)	["APPROVED"]
answerSource	array	No	Источник ответа (Answer source)	["SELLER"]
id	array	No	Массив ID вопросов (Question IDs)	["550e8400-..."]

Response Schema (200 OK):

{
  "data": [
    {
      "product": {
        "parentSku": "MP002XW0J7E6R",
        "sku": "MP002XW0J7E6R660",
        "externalSku": "77122JSS-8",
        "name": "Тоник для лица",
        "brand": "New Balance"
      },
      "items": [
        {
          "id": "550e8400-e29b-41d4-a716-446655440000",
          "createdAt": "2025-05-12T22:01:02.000Z",
          "dateAnswerUntil": "2025-05-15T22:01:02.000Z",
          "username": "Мария",
          "text": "Текст вопроса",
          "canAnswer": false,
          "answerSource": "SELLER",
          "status": "ANSWERED",
          "answers": [
            {
              "dateCreate": "2025-05-13T22:01:02.000Z",
              "text": "Текст ответа",
              "source": "SELLER",
              "status": "APPROVED",
              "rejectReason": "Причина отклонения"
            }
          ]
        }
      ]
    }
  ],
  "meta": {
    "total": 87,
    "page": 1,
    "limit": 100,
    "totalPages": 1
  }
}

Status Enums:

• QuestionStatus:

  • NEW - Новый (New)
  • IN_PROGRESS - В процессе (In progress)
  • ANSWERED - Отвечен (Answered)
  • REJECTED - Отклонен (Rejected)

• QuestionAnswerStatus:

  • APPROVED - Утвержден (Approved)
  • ON_MODERATION - На модерации (On moderation)
  • REJECTED - Отклонен (Rejected)

• QuestionAnswerSource:

  • SELLER - Продавец (Seller)
  • LAMODA - Lamoda

13.2 Answer Feedback Question

Endpoint: POST /v2/feedback/questions/{questionId}/answer

Description: Метод записи ответа на вопрос (Answer customer question)

Path Parameters:

Parameter	Type	Required	Description	Example
questionId	string	Yes	ID вопроса (Question ID)	"550e8400-e29b-41d4-a716-446655440000"

Request Schema:

{
  "sellerId": "242541217",
  "text": "Текст ответа на вопрос"
}

Request Parameters:

Parameter	Type	Required	Description	Example
sellerId	string	Yes	Идентификатор продавца (Seller ID, must match JWT)	"242541217"
text	string	Yes	Текст ответа (Answer text, min 1, max 1000 chars)	"Текст ответа"

Response Schema (200 OK):

{
  "questionId": "550e8400-e29b-41d4-a716-446655440000",
  "createdAt": "2025-05-12T22:01:02.000Z",
  "text": "Текст ответа",
  "source": "SELLER",
  "status": "ON_MODERATION",
  "rejectReason": "Причина отклонения"
}

Response Codes:

• 200 OK: Answer accepted
• 400 Bad Request: Validation error
• 401 Unauthorized: Token missing or invalid
• 403 Forbidden: Access denied
• 404 Not Found: Resource not found
• 503 Service Unavailable: Service unavailable

---

Response Codes

Common HTTP response codes across all endpoints:

Code	Description
200 OK	Request successful
201 Created	Resource created successfully
400 Bad Request	Invalid parameters
401 Unauthorized	Authentication required or token invalid
403 Forbidden	Access denied
404 Not Found	Resource not found
429 Too Many Requests	Rate limit exceeded
500 Internal Server Error	Server error
503 Service Unavailable	Service temporarily unavailable

---

Error Response Format

Standard error response format:

{
  "error": {
    "code": "VALIDATION_FAILED",
    "message": "Проверьте переданные данные",
    "details": [
      {
        "field": "sellerId",
        "issue": "Обязательное поле"
      }
    ]
  }
}

Error Codes:

• VALIDATION_FAILED - Validation error
• UNAUTHORIZED - Authentication required
• FORBIDDEN - Access denied
• NOT_FOUND - Resource not found
• SERVICE_UNAVAILABLE - Service unavailable

---

Authentication

All API requests require Bearer token authentication:

Authorization: Bearer <access_token>

Tokens can be obtained via OAuth2 authentication (see subtask-2-1-authentication.md).

---

Rate Limits

• B2B Platform API: See subtask-2-3-rate-limits.md
• Seller JSON-RPC API: See subtask-2-3-rate-limits.md
• Seller REST API: Maximum 1000 items per page for most endpoints

---

Notes

1. Date Formats:

   • Dates are typically in ISO 8601 format: YYYY-MM-DD or YYYY-MM-DDThh:mm:ssZ
   • Time zones are specified as offsets from UTC (e.g., +03:00)

2. Pagination:

   • Most list endpoints support pagination with page and limit parameters
   • Default page size is typically 25-100 items
   • Maximum page size varies by endpoint (typically 100-1000)

3. Filtering:

   • Many endpoints support filtering by various parameters
   • Filter parameters are often combined with OR logic

4. KLADR Codes:

   • KLADR (КЛАДР) codes are Russian address classifier codes
   • Format: 13-21 digit alphanumeric strings
   • Used for precise address identification

---

See Also

• Authentication Documentation
• Base URLs Documentation
• Rate Limits Documentation
• Business Models Documentation
• API Sections Catalog
• Products/Nomenclatures API
• Orders API
• Returns API
• Prices API
• Stocks API
• Shipments API

---

Document Version: 1.0 Last Updated: 2025-02-10 Maintained By: Auto-Claude Documentation System