Citilink Scraper - Russian Electronics Store Products
Pricing
from $3.00 / 1,000 results
Citilink Scraper - Russian Electronics Store Products
Scrape Citilink.ru, one of Russia's largest electronics and appliance retailers. Search products by keyword, browse any category, or fetch full product details - pricing, ratings, specifications, images, and stock status.
Pricing
from $3.00 / 1,000 results
Rating
0.0
(0)
Developer
Crawler Bros
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
Citilink Scraper
Scrape Citilink.ru, one of Russia's largest electronics, computer, and home-appliance retailers. Search products by keyword, browse any catalog category, pull full specifications for individual products, or fetch full-text customer reviews — no login, cookies, or API key required.
What this actor does
- Search — run a free-text keyword search (e.g.
iphone,ноутбук,телевизор) and get back matching products with price, rating, and availability. - Browse a category — pull every product listed under any Citilink catalog category (smartphones, laptops, TVs, appliances, etc.) by slug or URL.
- Product details — fetch full specifications, description, price, color variants, variant axes (colour/storage/etc.), and images for one or more products by ID or URL.
- Reviews — fetch full-text customer reviews (title, body, view count, likes/dislikes) for one or more products by ID or URL — distinct from the star-rating opinion summary already included in product details.
- Empty fields are omitted from every record — a field only appears when Citilink actually supplied a value for it.
Output: per-product (search / byCategory)
id— Citilink product IDname,shortName— Product titleslug— Citilink's URL slug for the productproductUrl— Canonical product page URLisAvailable— Whether the product is currently purchasablepriceCurrent,priceOld,discountPercent,bonusPoints— Pricing (RUB)categoryId,categoryName— Catalog categorybrand— Brand namerating,opinionsCount,reviewsCount— Customer feedbackproperties— Key specs shown on the listing card (name/value pairs)images,imageUrl— Product photo URLsmultiplicity— Minimum purchasable quantity increment, when above 1accessMode— Citilink's own visibility/sale mode for the listingearliestDeliveryDate— Earliest self-pickup/delivery date, if availablelabels— Promotional badges (installment plans, bundles, etc.)sourceUrl,scrapedAt,recordType— Standard metadata
Output: per-product (productDetails)
All of the fields above, plus:
originalProductId— Citilink's underlying product ID (differs fromidfor some listings)description— Full product description (plain text)properties— Full specification list, each with an optionalmeasure(unit)categorySlug,categoryPath— Category slug and full breadcrumb (root → leaf)brandId,brandName— Brand ID and namevendorCode— Manufacturer/vendor codeaccessoriesCount,discussionsCount,documentationsCount,servicesCount,videosCount— Per-section content counterscolorVariants— Sibling products in other colors, each with its ownid,productUrl,color,isAvailable, andimageUrlvariantGroups— Every variant axis the product exposes (colour, storage, etc.), each with its sibling-product options — not just colour
Product details also opportunistically include the following, when Citilink's own page loads them in time:
ratingBreakdown— Star-by-star opinion histogram:[{stars, count, percentage}, ...]topReview— Citilink's own featured customer opinion —text,pros,cons,rating,date,authorNickname,verifiedPurchase,likes,dislikesrelatedProducts— "Bought together" complementary products (same fields as search results)similarProducts— "Similar products" alternatives (same fields as search results)courierDelivery— Fastest courier option —price(RUB),eta,typepickupStoresAvailable— Number of pickup points with stock on the earliest available day
Output: per-review (mode = reviews)
productId— Citilink product ID the review belongs toreviewId— Citilink's own review IDtitle— Review headlinecontent— Full review body (plain text/markdown as authored, including any embedded image links)viewsCount— Number of times the review has been viewedcreatedAt,modifiedAt— Timestamps (modifiedAtonly present when it differs fromcreatedAt)authorSuid— Author's public site IDauthorNickname— Author's display nickname, if setlikes,dislikes— Helpful-vote counts (only present when non-zero)sourceUrl,scrapedAt,recordType— Standard metadata
Input
| Field | Type | Default | Description |
|---|---|---|---|
mode | string | search | search / byCategory / productDetails / reviews |
searchQuery | string | iphone | Free-text keyword (mode=search) |
category | string | – | Category slug (smartfony), catalog path, or full URL (mode=byCategory) |
productIds | array | [] | Product IDs or full product URLs (mode=productDetails, reviews) |
maxReviewsPerProduct | int | 20 | Cap on reviews fetched per product ID (1-200, mode=reviews) |
sortBy | string | relevance | relevance / priceAsc / priceDesc / discount / rating / opinions / reviews (mode=search, byCategory) |
minPrice | int | – | Drop products cheaper than this, RUB (mode=search, byCategory) |
maxPrice | int | – | Drop products more expensive than this, RUB (mode=search, byCategory) |
minRating | number | – | Drop products rated below this, 0-5 scale (mode=search, byCategory) |
inStockOnly | boolean | false | Only return purchasable products (mode=search, byCategory) |
maxItems | int | 10 | Hard cap on emitted records (1-500) |
proxyConfiguration | object | AUTO group | Apify proxy — required; the default AUTO (datacenter) group is sufficient |
How sorting works
When sortBy=relevance (the default), results are returned in Citilink's own order. For any
other sortBy value, the actor gathers a wider window of results in relevance order, sorts that
window by the requested key, then truncates to maxItems. This means non-relevance sorts reorder
the fetched window rather than Citilink's entire catalog — for the most accurate top-N on a very
broad category, narrow the search with a keyword or price filter first.
Example: search with price and rating filters
{"mode": "search","searchQuery": "ноутбук","minPrice": 30000,"maxPrice": 100000,"minRating": 4,"sortBy": "priceAsc","maxItems": 50}
Example: browse a category in stock only
{"mode": "byCategory","category": "smartfony","inStockOnly": true,"sortBy": "discount","maxItems": 100}
Example: fetch full product details
{"mode": "productDetails","productIds": ["2143346","https://www.citilink.ru/product/televizor-samsung-qe65q80dauxru-65-4k-ultra-hd-3840x2160-2135640/"],"maxItems": 10}
Example: fetch customer reviews
{"mode": "reviews","productIds": ["2143346"],"maxReviewsPerProduct": 50}
Use cases
- Track pricing and discounts on specific product categories (e.g. all
smartfonyunder 50,000 RUB). - Monitor stock availability for a watchlist of products by ID.
- Build a price-comparison feed of Citilink search results for a set of keywords.
- Pull full specifications for a batch of products to enrich your own catalog.
- Analyze full-text customer reviews for a set of products (sentiment, common complaints, helpful-vote counts) beyond the star-rating summary.
Other Russian marketplace actors by CrawlerBros
FAQ
Do I need a Citilink account or API key? No. The actor scrapes publicly available product data with no authentication.
Why does this actor require a proxy? Citilink blocks automated requests without a working proxy session. The default AUTO (datacenter) proxy group is sufficient — residential proxy is not required.
Why is sortBy not a perfect global sort?
See "How sorting works" above — it's applied across the fetched result window, not Citilink's
full catalog, to keep run times predictable.
Can I search in Russian?
Yes — searchQuery and category both accept Cyrillic text/slugs directly.
Why do some listing records have fewer specs than product-detail records?
Search/category results include only the handful of "short" specs Citilink shows on the
listing card. Use mode=productDetails for the full specification list.
What's the difference between topReview/ratingBreakdown and mode=reviews?
topReview and ratingBreakdown (in mode=productDetails) summarize the star-rating "opinions"
customers leave when rating a product. mode=reviews fetches Citilink's separate, longer-form
written reviews (with a title and full body text) — a smaller, distinct pool of content some
products don't have at all.
Why don't ratingBreakdown, topReview, relatedProducts, similarProducts, or
courierDelivery appear on every product?
These sections load on the product page after the core content, and Citilink doesn't always
render them in time. When that happens the core record (name, price, specs, images, etc.) is
still returned in full — only the enrichment fields are omitted, never filled with placeholder
data.
Why don't productUrl links open with a plain script or curl request?
Citilink's product and category pages require a real browser session to load; a script-only
request without a browser is blocked. The URLs themselves are correct and open normally in any
browser. Product image URLs (cdn.citilink.ru/...) are on a separate, unprotected host and load
directly anywhere.
Is this actor affiliated with Citilink? No, this is a third-party actor that reads publicly available data from citilink.ru.