POST /api/citilink/products/similar
Price: 20 credits
List the products citilink.ru links to one product — close substitutes, direct analogues, cross-sell accessories, the cheaper picks it suggests and its discounted counterparts — each priced for the requested city and tagged with the relation it came from.
`relation` says why each row is here, and the kinds are not interchangeable: `analog` is a replacement for the same job, `accessory` is something bought alongside it, so filter on it rather than treating the list as one pool. Several relations are frequently empty for a given product; that is the site having nothing to suggest, not a failure. Prices follow `city` like everywhere else on this platform.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)city string — Citilink city code that the returned prices, stock and delivery belong to. Codes come from citilink/cities; the response echoes the resolved city back in `city` (default: "msk_cl"; examples: "msk_cl", "kzn_cl", "nvs_cl", "abn_cl:5x0050435"; minLength: 1)product string required — Citilink product page URL or the product code printed on the page as 'Код товара' (examples: "2019135", "M00300851", "https://www.citilink.ru/product/noutbuk-digma-pro-fortis-m-i5-1235u-16gb-ssd512gb-2019135/"; minLength: 1)count integer required — Max number of related products to return (min: 1)with_images boolean — Include the product image gallery on every row (default: false)relations array — Which kinds of relation to include; all of them when left empty (default: []; one of: "similar", "analog", "accessory", "optimal_choice", "discounted")@type string (default: "CitilinkRelatedProduct")id string requiredcity string nullablecity_name string nullablename string nullableshort_name string nullablealias string nullableurl string nullablebrand object nullable@type string (default: "CitilinkBrandRef")id string nullablename string nullablealias string nullableurl string nullableimage string nullablevendor_site string nullablecategory object nullable@type string (default: "CitilinkCategoryRef")id string nullablename string nullablealias string nullableurl string nullableprice number nullableold_price number nullableclub_price number nullableclub_price_view_type string nullablediscount_percent integer nullablebonus_points integer nullablesbp_bonus integer nullableis_fair_price boolean nullablecurrency string (default: "RUB")is_available boolean nullableis_discount boolean nullablerating number nullableopinion_count integer nullablereview_count integer nullablestock_in_stores integer nullablemax_stock_in_store integer nullablepickup_points array (default: [])@type string (default: "CitilinkPickupSummary")delivery_date string nullablestore_count integer nullableimage string nullableimages array (default: [])labels array (default: [])@type string (default: "CitilinkLabel")kind string nullablename string nullabledescription string nullableurl string nullableaction_id string nullableexpires_at string nullablekey_properties array (default: [])@type string (default: "CitilinkProperty")name string requiredvalue string requiredmeasure string nullabledescription string nullablegroup string nullablepack_size integer nullablesupplier_pack_size integer nullablehas_analog_products boolean nullableaccess_mode string nullablerelation string nullablesource_product_id string nullable422 — Unknown city code — take one from citilink/cities. Check the fields against this schema. A URN with the wrong prefix is the most common cause.408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.412 — No such product on citilink.ru — the code or URL resolves to nothing. Retrying will not help: either the entity does not exist, or the input points at a different one.429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.X-Retry-After — Seconds to wait before retrying. Present only on 429.