Turbo.az Scraper — Azerbaijan Used Car Prices
Pricing
from $2.10 / 1,000 results
Turbo.az Scraper — Azerbaijan Used Car Prices
Scrape Turbo.az, Azerbaijan's largest car marketplace. Extract make and model, price and currency, model year, engine size, mileage, city, listing date, dealer flag and photos across new and used cars.
Pricing
from $2.10 / 1,000 results
Rating
0.0
(0)
Developer
Logiover
Maintained by CommunityActor stats
0
Bookmarked
10
Total users
2
Monthly active users
9 days ago
Last modified
Categories
Features
Share
Azerbaijan's largest car marketplace in rows: make and model, price and currency, model year, engine size, mileage, city, listing date, seller type and photos — new and used cars.
What does the Turbo.az Scraper do?
This Actor collects car listings from Turbo.az, by far the largest vehicle marketplace in Azerbaijan and the country's reference for what a car is worth. It returns make and model, the asking price, model year, engine capacity, mileage, city and how recently the listing was posted.
Two details on this market needed handling rather than assuming. Prices are quoted in three currencies on the same page — manat, dollars and euros — so the currency is detected per listing instead of being assumed, which would otherwise mix three units silently in one column. And the seller is not a simple dealer/private split: the site marks an official brand dealer (Rəsmi) separately from an independent showroom (Salon), with unmarked listings being private sellers. All three are kept apart, because that distinction is exactly what a trader is looking at.
Who is it for?
- Car dealers and importers benchmarking asking prices in the Azerbaijani market.
- Valuation and price-guide services building residual-value curves.
- Market researchers measuring supply by make, year and engine size.
- Fleet and leasing companies tracking resale values.
- Analysts watching import patterns into the Caucasus.
- Marketplaces seeding an Azerbaijani vehicle catalogue.
Use cases
- Track asking prices for a make and model by model year.
- Compare official dealer pricing against private-seller pricing on the same car.
- Measure how mileage moves price within one model year.
- Watch new-listing volume as a demand indicator.
- Build a depreciation curve from year and price across the market.
- Separate brand-new stock (0 km) from used supply.
- Feed an AI agent live car prices for valuation questions.
Why use this Turbo.az Scraper?
- Currency detected per listing — manat, dollars and euros never mixed into one number.
- Seller type split three ways — official dealer, showroom, private.
- Zero mileage preserved as
0, so brand-new stock is visible rather than blank. See the FAQ. - Year, engine size and mileage parsed into numbers you can filter on.
- Thirty-six listings per page with pages fetched in parallel.
- Keyless and login-free.
What data can you extract?
One row per listing. Anything the source left blank comes back as null.
| Field | Description |
|---|---|
listingId | Turbo.az listing ID |
url | Link to the listing |
title | Make and model |
price | Asking price |
currency | AZN, USD or EUR, detected per listing |
modelYear | Model year |
engineLitres | Engine capacity in litres |
mileageKm | Mileage in kilometres |
city | City |
publishedText | Listing date as the site shows it |
sellerType | Official dealer, Showroom or Private |
imageUrl | First photo |
scrapedAt | ISO timestamp of collection |
Sample output
{"listingId": "9835383","url": "https://turbo.az/autos/9835383-jac-t6","title": "JAC T6","price": 37900,"currency": "AZN","modelYear": 2025,"engineLitres": 2,"mileageKm": 0,"city": "Bakı","publishedText": "bugün 09:17","sellerType": "Official dealer","imageUrl": "https://turbo.azstatic.com/uploads/f460x343/2025/10/08/jac-t6.jpg","scrapedAt": "2026-08-22T09:17:04.388Z"}
How to use the Turbo.az Scraper
Option A — the whole market
Leave Section as autos, set Maximum results and run.
Option B — another vehicle type
Set Section to another slug from a Turbo.az URL, such as motorcycles.
Option C — a price watch
Schedule a daily run and diff by listingId to track what sold and what changed price.
Input parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
section | string | autos | Section as it appears in a Turbo.az URL |
maxResults | integer | 1000 | Stop after this many listings (max 50,000) |
proxyConfiguration | object | AZ residential | Turbo.az serves Azerbaijani exits |
Tips for best results
- Always group by
currencybefore averaging. A €30,000 car and a ₼30,000 car are not the same car, and both appear in the same category. sellerTypematters more than it looks. Official dealer stock is mostly new and priced to list; private stock is used and negotiable. Mixing them flattens the signal.mileageKm: 0means new, not missing. Filter on it to separate new stock from used.- Use
modelYearwithmileageKmtogether for any depreciation work; either alone is misleading. - Deduplicate on
listingIdwhen combining scheduled runs.
Integrations
Connect the dataset to Make, Zapier, Airbyte, Google Sheets, Slack, GitHub or any HTTP endpoint through Apify integrations, or schedule a run and push results into a warehouse with a webhook.
API usage
from apify_client import ApifyClientclient = ApifyClient("<YOUR_API_TOKEN>")run = client.actor("logiover/turbo-az-car-scraper").call(run_input={"section": "autos","maxResults": 3000,})rows = list(client.dataset(run["defaultDatasetId"]).iterate_items())used = [r for r in rows if r["currency"] == "AZN" and (r["mileageKm"] or 0) > 0]print(len(used), "used cars, median price ₼",sorted(r["price"] for r in used)[len(used) // 2])
🤖 AI Agents, MCP & RAG Integration
The Actor is callable from the Apify MCP server, so an assistant can pull Azerbaijani car listings directly and answer valuation questions.
Connect this Actor directly to Apify AI, Claude Desktop, Cursor, VS Code, Windsurf, LangChain, or LlamaIndex via the official Apify MCP Server — no custom wrapper code needed:
{"mcpServers": {"apify": {"type": "http","url": "https://mcp.apify.com?tools=logiover/turbo-az-car-scraper"}}}
- Schema-typed inputs & outputs: Clean JSON records with explicit
.actor/input_schema.jsonand.actor/output_schema.jsondefinitions so LLM agents infer parameters and parse fields accurately without HTML noise. - Bounded & predictable runs: Built-in volume caps and pay-per-result budget guards prevent runaway agent tool loops.
- RAG & automation ready: Stream run datasets straight into vector stores, n8n, Make, Zapier, or webhook pipelines.
FAQ
Do I need a Turbo.az account or API key?
No. This Actor reads the public marketplace; there is nothing to register.
How many listings can one run return?
Up to 50,000 per run, thirty-six per page. Pages are fetched several at a time, so a few thousand listings take about a minute.
Why are there three currencies?
Because sellers in Azerbaijan quote in manat, dollars or euros depending on the car and the buyer they are targeting. The site does not normalise them, so this Actor labels each listing with the currency actually shown rather than assuming manat and silently corrupting the column.
Why is mileage sometimes zero?
Because the car is brand new. Zero is a real value here, so it is kept as 0 rather than blanked — filtering on it is the cleanest way to separate new stock from used supply.
What is the difference between an official dealer and a showroom?
Rəsmi marks an official brand dealer, Salon an independent car showroom, and an unmarked listing is a private seller. All three price differently, so they are kept as separate values rather than collapsed into one dealer flag.
Does it collect the seller's phone number?
No. Contact details sit behind the individual listing page. Every row carries a url to it.
Are titles in Azerbaijani?
Make and model come through as written — mostly Latin-script Latin brand names — while the city and the date label are in Azerbaijani, exactly as published.
Can I export to CSV or Excel?
Yes — every run's dataset exports to JSON, CSV, Excel, XML or JSONL.
How fresh is the data?
Each run reads the marketplace live, so results are as current as Turbo.az itself.
Why did my run return zero listings?
Usually a section slug that does not exist. Use autos to check, then copy other slugs from a Turbo.az URL.
💬 Support, Issues & Reviews
- Bug reports & target-site changes: Hit an unexpected empty result or selector change? Open a ticket in the Issues tab with your Run ID or sample input — we actively monitor issues and ship fixes fast.
- Feature & field requests: Need an additional data attribute or filter? Request it in the Issues tab.
- Enjoying this Actor? If it saved you engineering time, please consider leaving an honest review on Apify Store or bookmarking logiover/turbo-az-car-scraper — organic developer feedback helps others discover reliable tools and keeps maintenance prioritized.
Is it legal to scrape Turbo.az?
Turbo.az is a public marketplace and this Actor reads only its public listing pages — no accounts, no logins. Vehicle details and asking prices are commercial listings published for public view. You remain responsible for how you use the data and for respecting the marketplace's terms in your own jurisdiction.
This Actor is an independent tool. It is not affiliated with, endorsed by, or sponsored by Turbo.az; Turbo.az and all other trademarks mentioned here are the property of their respective owners.
Output example
One row from a real run of this Actor:
{"listingId": "9143116","url": "https://turbo.az/autos/9143116-bestune-t55","title": "Bestune T55","price": 28500,"currency": "AZN","modelYear": 2026,"engineLitres": 1.5,"mileageKm": 0,"city": "Bakı","publishedText": "bugün 11:15","sellerType": "Official dealer","imageUrl": "https://turbo.azstatic.com/uploads/f460x343/2025%2F01%2F24%2F15%2F16%2F07%2F90df9d13-03ac-…","scrapedAt": "2026-08-22T09:58:39.561Z"}
Related scrapers
Other Actors from the same collection:
How much Turbo.az data can you extract in one run?
A single run returned 845 vehicle listings in 38 seconds on the example input. That is roughly 1,334 vehicle listings a minute. Widen the search — more queries, more pages, a broader location — and the same run goes deeper.
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 Turbo.az 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.
📝 Changelog
2026-11-14
- Verified live production health run (2026-11-14): extracted 35 structured records in 3.7s with valid schema output.
- Hardened internal proxy stall fallback and pay-per-event dataset instance budget protection.
2026-11-11
- Added reliable terminal run status telemetry and structured Apify AI / MCP Server (
mcp.apify.com) tool configuration. - Added direct Issues & Reviews support links and refreshed live maintenance verification.
2026-11-01
- Monthly health check (2026-11-01): a live run on the current build completed successfully and returned data. Input options, output fields and pricing are unchanged.
- README refreshed: independence disclaimer added.
- README refreshed: duplicate "Related scrapers" sections merged.
2026-10-15
- The proxy field no longer needs a group chosen: the run uses residential exits pinned to AZ on its own, so the prefilled input works for every account.
- Every request now has a hard time limit, so a proxy connection that stalls can no longer hold up the run or push it past its timeout.
- A run that reaches its maximum cost per run now stops cleanly with its results saved and a status message, instead of ending as aborted.
- A proxy group your account cannot use no longer stops the run at start-up; it falls back to the default Apify Proxy.
- Runs with a short timeout (API and AI-agent calls) now finish inside it with what they collected, instead of being cut off.
- Memory is managed within the run's own limit, which removes a rare out-of-memory crash on large pages.
- The prefilled example for
maxResultsis now 333 (was 1,000). - The default used when the field is left out for
maxResultsis now 6,666 (was 1,000).
2026-09-23
- Fleet-wide quality audit. Verified end to end against live data and re-checked the input schema, the output columns and the run configuration.
- Output verified on a live run: 1000 row(s) across 13 columns, 99.7% of cells populated.
- Run reliability reviewed: 100.0% of public runs succeeded in the last 30 days.
- Input schema, output schema and pricing configuration reviewed.
2026-09-01
- Fleet-wide health check. Verified against this Actor's real run history: 30-day success rate, output row counts, per-field fill rates, and peak memory against the configured memory limit.
- Reviewed for the failure patterns that have cost this fleet runs — unguarded proxy setup, retry loops that can outlast the run's own time budget, and full-page HTML parsing that can exhaust a small container.
- No change to input, output fields or scraping logic.
1.0 (2026-08-22)
- First release. Azerbaijani car listings with price, model year, engine size, mileage and city.
*Maintained: last verified 2026-11-14 — checked end-to-end against live run history (reliability, output fields and types, and time/memory budgets).