Lamoda products with the real paid price, promotions and stock for every size

The price the buyer pays (price), the struck original price (was_price) with the computed discount_percent, the store's own discount figure (discount_percent_site), price_type (original, onsite markdown or onsite_promo) and, for a timed promotion, promotion with its percent and end time. In our 2026-10-15 sample 56 of 260 search rows and 142 of 420 listing rows were priced by a running promotion. A price that needs a promo code would be returned apart as promo_code_price; none appeared. Prices shown only after signing in (Lamoda Club) are not available.

It depends on the action, because Lamoda publishes different ceilings on different pages. search returns the real per-size figure (up to 480 seen). The category listing stops at 10 per size and the product card at 20 per size; on those, stock_capped tells you when the figure is the ceiling rather than the count.

The category listing groups colour variants of one model and can show sizes of a sibling SKU inside a row. Every size names its own product_id; the row's stock and availability count only its own sizes, and sizes_from_other_products lists the siblings (17 of 420 rows in our sample).

search: up to 50 rows a page and up to result 10 000 (the store's own ceiling); last_page tells you where it ends. category: 60 rows a page and up to page 167. total_results is the store's own count.

query, category_id, brand_id, gender (women, men, girls, boys, children, unisex) and color_id, one value each. Sorting, the sale filter and a keyword inside one category are on the category action. A price range is not offered: the store's price filter returned products outside the requested range in our tests.

On product: the seller's name and whether Lamoda itself or a marketplace partner sells it, and the legal owner's company name, shop name, tax number, registration number, address and the delivery terms the seller publishes.

One request to the store per call. Over three runs every positive call succeeded (69 of 69); median times were about 3.2 seconds for search, 4.4 to 5.2 seconds for category pages, 2.8 to 3.3 seconds for product cards and about 3 seconds for reviews, with the slowest calls around 9 seconds.

Lamoda API is a ReefAPI endpoint group for russia's lamoda fashion store as json: keyword search, category listings with the site's sorts and sale filter, full product cards with the price the buyer pays, every size with its stock, the seller, and customer reviews. It returns live JSON through POST requests under /lamoda/v1.

Yes. ReefAPI starts with 1,000 free credits, no card required. Lamoda calls use the same shared credit balance as every other ReefAPI engine.

No login to Lamoda is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.

The page example is captured from a live search call, and production requests fetch live data through ReefAPI rather than a static sample.

Lamoda actions currently cost 1-3 credits per successful call. Failed or blocked calls are free. All APIs draw from one credit pool.

Yes. Connect ReefAPI once through MCP and your assistant can call lamoda actions with the same key, credit pool and JSON envelope used by normal REST requests.

It is the managed alternative to a DIY Lamoda scraper. Instead of building and maintaining your own scraper — proxies, headless browsers, captcha and constant breakage — you call one ReefAPI endpoint and get the same russia's lamoda fashion store as json: keyword search, category listings with the site's sorts and sale filter, full product cards with the price the buyer pays, every size with its stock, the seller, and customer reviews back as clean JSON.