/citilink/products/stores

POST /api/citilink/products/stores

Price: 20 credits

List every citilink.ru pickup point that can hand over one product in a given city, with the number of units each one holds right now, the pickup fee and the date the unit arrives, plus the point's address, coordinates, opening hours, phone, kind and delivery partner.

How to use it

This is the only place stock is broken down per point; citilink/products gives the city totals instead. `available_count` is zero on most rows — those points can receive the unit by `delivery_date` but do not hold it, so set `in_stock_only` when you mean stock on a shelf today. A large Russian city returns thousands of points, the overwhelming majority of them partner pickup points (`formats: [partner]`), with true parcel lockers a small minority of those — narrow with `formats` unless you genuinely want the whole network.

Parameters

• access-token string required

Request body

• timeout 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 pickup points to return (min: 1)
• in_stock_only boolean — Keep only pickup points that hold at least one unit right now (default: false)
• formats array — Keep only pickup points of these kinds (default: []; one of: "shop", "pickup_point", "partner")

Response

• @type string (default: "CitilinkStoreStock")
• id string required
• store_id string required
• product_id string required
• city string nullable
• city_name string nullable
• available_count integer nullable
• delivery_price number nullable
• delivery_date string nullable
• name string nullable
• short_name string nullable
• address string nullable
• store_city_name string nullable
• space_id string nullable
• store_format string nullable
• store_format_name string nullable
• sub_format string nullable
• external_format string nullable
• is_new boolean nullable
• services array (default: [])
• serving_type string nullable
• shipping_agent string nullable
• work_hours string nullable
• delivery_info string nullable
• is_passport_required boolean nullable
• latitude number nullable
• longitude number nullable
• phone string nullable

Errors

• 422 — 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.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-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.