Kolesa.kz Scraper — Kazakhstan Car Listings & Prices
Pricing
from $15.00 / 1,000 results
Kolesa.kz Scraper — Kazakhstan Car Listings & Prices
Scrape job postings for Switzerland from Talent.com: title, hiring company, city, quick-apply flag, update recency and a description snippet. Keyless, no login. Export JSON, CSV or Excel.
Pricing
from $15.00 / 1,000 results
Rating
0.0
(0)
Developer
Logiover
Maintained by CommunityActor stats
0
Bookmarked
5
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
Export vehicle listings from Kolesa.kz, Kazakhstan's largest car marketplace — price, year, engine, fuel, gearbox and mileage — to JSON, CSV or Excel. Keyless, no login.
What does Kolesa.kz Scraper do?
Kolesa renders its results server-side, so this Actor parses the cards directly and walks the pagination. No API key, no account, no cookies.
The whole vehicle specification is published as one Russian sentence: 2011 г., Б/у внедорожник, 4.7 л, бензин, КПП автомат, 225 000 км. Nobody can filter by mileage or fuel type while that sits in a text column, so this Actor splits it into year, bodyAndCondition, engineLitres, fuel, gearbox and mileageKm.
Two details in that split matter. Russian uses a comma as the decimal separator, so a naive split on , tears 3,0 л into 3 and 0 л and reports a zero-litre engine — the Actor splits on comma-plus-space instead. And the litre marker л is Cyrillic, so an ASCII word boundary never matches it; the pattern is written to handle that. Both were real bugs caught in testing, not hypotheticals.
Who is it for?
- Car dealers benchmarking asking prices across Kazakh cities.
- Price analysts building depreciation curves by model and year.
- Importers and exporters spotting arbitrage between regions.
- Marketplace builders who need a Kazakh vehicle feed.
- Researchers measuring fleet age, fuel mix and gearbox split.
Use cases
- Compare asking prices for a model between Almaty, Astana and Aktobe.
- Build a mileage-versus-price curve for a specific year range.
- Track how many diesel versus petrol cars are listed each week.
- Filter to verified sellers to build a dealer list.
- Export a snapshot with specs for a valuation model.
Why use this Actor?
- Keyless — no account, no token, no login.
- Specs as real columns — year, engine, fuel, gearbox and mileage are parsed out, not left in prose.
- Correct Russian number handling —
3,0 лreads as 3.0, not 0. - Sortable price alongside the original label.
- Verified-seller flag for dealer prospecting.
- Time-budgeted — a slow page ends the run cleanly with rows saved.
What data can you extract?
Every row carries the listing identity and URL, the price in label and numeric form, the full spec line as published, the six parsed spec columns, the city and whether Kolesa marks the seller as verified. See the Output tab for types.
How to use it
- Pick the section — cars, motorcycles, trucks or special vehicles.
- Optionally set a city and a price band.
- Set Maximum results and run, then export JSON, CSV or Excel.
Input example
{"section": "cars","city": "almaty","maxPrice": 15000000,"maxResults": 1000}
Notes and limits
- Mileage is absent on new vehicles; those rows keep
mileageKmasnullrather than zero, because zero would distort any average. - Listing text is in Russian, as sellers write it.
- Prices are asking prices, not transaction prices.
- This Actor exports result cards, not full listing pages — that is what keeps bulk runs cheap. Open the listing URL for photos and seller contact.
- You are responsible for how you use listing and seller data.
FAQ
Do I need a Kolesa account? No. Listings are public and this Actor needs nothing from you.
Are the specs reliable?
They come from Kolesa's own spec line and are split field by field. Where a field is missing from the ad, the column is null rather than guessed.
Can I scrape trucks or motorcycles? Yes, switch the section input.
Is mileage numeric?
Yes — 225 000 км becomes 225000, ready to sort or chart.
How am I charged? Pay per result — you pay for the listings delivered.
*Maintained: last verified 2026-09-01 — checked end-to-end against live run history (reliability, output fields and types, and time/memory budgets).
Output example
One row from a real run of this Actor:
{"listingId": "229599472","title": "Toyota Camry","listingUrl": "https://kolesa.kz/a/show/229599472","priceLabel": "5 800 000 ₸","priceAmount": 5800000,"currency": "KZT","specs": "2008 г., Б/у седан, 2.4 л, бензин, КПП автомат, с пробегом 285 000 км, серый, металлик,…","year": 2008,"bodyAndCondition": "Б/у седан","engineLitres": 2.4,"fuel": "бензин","gearbox": "автомат","mileageKm": 285000,"city": "Алматы","verifiedSeller": false,"country": "Kazakhstan","source": "kolesa_kz","scrapedAt": "2026-09-01T08:38:40.158Z"}
Output fields
| Field | Type | Filled in sample |
|---|---|---|
listingId | string | 100% |
title | string | 100% |
listingUrl | string | 100% |
priceLabel | string | 100% |
priceAmount | number | 100% |
currency | string | 100% |
specs | string | 100% |
year | number | 100% |
bodyAndCondition | string | 100% |
engineLitres | number | 98% |
fuel | string | 98% |
gearbox | string | 100% |
mileageKm | number | 81% |
city | string | 100% |
verifiedSeller | boolean | 100% |
country | string | 100% |
source | string | 100% |
scrapedAt | string | 100% |
Is it legal?
This Actor collects only publicly available data — the same content any visitor to Kolesa.kz can see without logging in. It does not bypass authentication and does not gather private information. How you use the output is your responsibility: respect the source's terms, applicable copyright, and data-protection law such as GDPR where personal data is involved.
Related scrapers
Other Actors from the same collection:
Scheduling and integrations
Run this Actor on a schedule — hourly, daily or weekly — and have every run append to the same dataset, which is how you turn a one-off export into a time series. Results can be pushed straight into Google Sheets, Slack, Zapier, Make, Airtable or any Webhook.
How much Kolesa.kz data can you extract in one run?
A single run returned 1,000 listings in 79 seconds on the example input, and it was still going when the measurement stopped — raise the result limit and it keeps paginating. That is roughly 759 listings a minute.
There is no hard ceiling built into this Actor. What bounds a run is the result limit you set, the breadth of the input you give it, and how much Kolesa.kz itself publishes. Because billing is per result, a wider run costs proportionally more and a narrow one costs almost nothing — so it is worth starting small and scaling once the output looks right.
Kolesa.kz scraping — frequently asked questions
Do I need a Kolesa.kz API key, account or login?
No. This Actor reads publicly available pages and feeds, so there is nothing to register for and no credentials to manage.
How do I export Kolesa.kz data to CSV, Excel, JSON or Google Sheets?
Open the Storage tab after a run and pick the format you want — CSV, Excel, JSON, XML or an HTML table. For Google Sheets, Airtable or a database, use the dataset URL or the Apify API so the sheet refreshes itself on every run.
Can I schedule this Kolesa.kz scraper to run daily or hourly?
Yes. Use the Schedules tab and pick a cadence. Daily is enough for most tracking work; pick hourly only if the listings you care about really do change that fast.
How many listings can I get, and what does it cost?
See the volume section above for a measured figure. Billing is per result, so you pay for the rows you actually receive and a run that finds nothing costs nothing.
Is scraping Kolesa.kz legal?
This Actor collects only information that Kolesa.kz publishes publicly. It does not log in, does not defeat access controls and does not touch private data. You remain responsible for how you use the output, including under GDPR and similar rules where personal data is involved.
What happens if Kolesa.kz blocks the run or changes its layout?
A refused exit IP is swapped for a fresh one within a quarter of a second and retried, and rate limiting is waited out rather than fought. If nothing gets through, the run fails with the reason instead of reporting success with zero rows — so an empty result always means "no matches", never "the source would not answer".
Can I use this with an AI agent, LangChain or an MCP client?
Yes. The Actor is callable over the Apify API and through Apify's MCP server, so an agent can run it and read the dataset back as a tool call.