Complete Guide: How to Scrape Standvirtual Car Listings Using Python
Run the Standvirtual Scraper Apify Actor from Python and get standvirtual.com prices, year, mileage, power and seller type as clean JSON rows.

This complete guide to Standvirtual Scraper shows how to run a standvirtual.com scraper from Python through the Apify API and get back typed listing rows: price in euros, first-registration year, mileage in kilometres, fuel, gearbox, engine power, town and district, seller type, and the dealer's name where there is one.
Standvirtual is a Portuguese marketplace for cars and motorbikes. Two things make a hand-written crawler more work than it looks. First, the listing data sits in a JSON block inside the page, with the search results nested in it as a JSON string. Second, the site's keyword search is fuzzy: a "golf gti" search also returns other cars.
You will automate the extraction with the Standvirtual Scraper Apify Actor (reventadata/standvirtual-scraper). Prerequisites are minimal: Python 3.11+, the official apify-client package, and an Apify API token. Estimated time to complete: one sitting. The sample rows in this guide are a sample from a capture dated 2026-10-20, parsed with the Actor's own code; this guide quotes no run.
TL;DR
In this tutorial, you'll learn to start the Standvirtual Scraper Apify Actor from Python, wait for the run, and read its dataset. Key steps: install apify-client, export APIFY_API_TOKEN, describe the search in run_input (searchQueries, category, make, price, year and mileage ranges, fuelType, sortBy), call the Actor, then read the items from run.default_dataset_id.
Expected outcome: a JSON list of Standvirtual listings with price, year, mileage, engine power, district and seller type, ready for a spreadsheet, database or analysis script.
The Actor is at apify.com/reventadata/standvirtual-scraper.
Prerequisites and setup
To follow this tutorial, you will need:
- Python 3.11+ installed locally (
apify-client3.x requires it). - The Apify API client for Python.
- An Apify account and API token.
Sign up for an Apify account first. Apify Console is the web interface where runs, datasets and tokens are managed; your token is on the API & Integrations page. Keep the token out of any file you commit: the snippets below read it from the environment, so the same script runs on a laptop, a server or in CI. The platform documentation starts at docs.apify.com.
Install the client:
pip install "apify-client~=3.0"
Set your API token in your environment:
export APIFY_API_TOKEN="your_apify_token_here"
Understanding Standvirtual Scraper
How it works behind the scenes
- The site's own search URL. The keyword goes in the path (
/carros/q-golf-gti), as the site's search box does; without a keyword the make goes there (/carros/bmw). Price, year, mileage, fuel and sort go in the query string, so Standvirtual filters first. - No proxy by default.
proxyConfigurationis off unless you turn it on. - Numeric fields. The Actor reads the listings, so mileage, power and engine capacity come out as integers.
- Pages. It walks
?page=2,?page=3and so on, 32 listings per page, untilmaxPages,maxItemsor the last page of results. Duplicate listing ids are skipped. - The keyword check. With
requireKeywordMatchon (the default), a title must contain every search word, ignoring case and accents.
Limitations to be aware of
- No model filter: Standvirtual ignores a model in the URL; put the model in the search term.
- No listing pages: no full ad text, and no phone numbers or e-mails.
- Private sellers have no name in the data.
Step-by-step walkthrough
Step 1: Initialize the client and define inputs
Create the client from your environment token and describe the search. This example asks for one page of "golf gti" cars in Standvirtual's own order:
import os
from apify_client import ApifyClient
# 1. Initialize ApifyClient with token from environment
client = ApifyClient(os.environ["APIFY_API_TOKEN"])
# 2. Define the search: "golf gti" cars, one page in Standvirtual's own order
run_input = {
"searchQueries": ["golf gti"],
"sortBy": "relevance",
"maxPages": 1,
}
(Note: the sample rows in this guide come from page 1 of this same search, "golf gti" cars in Standvirtual's Recommended order, captured on 2026-10-20. That page held 32 listings out of 145 results; 27 had both words in the title.)
Two more configurations that use the same fields:
- Electric cars from 2022 on, newest first:
{"fuelType": "electric", "minYear": 2022, "maxItems": 200}. - BMW cars under 20,000 EUR and 100,000 km:
{"make": "bmw", "maxPrice": 20000, "maxMileage": 100000, "sortBy": "priceAsc", "maxItems": 100}.
Step 2: Trigger execution on Apify
.call(run_input=run_input) starts the run and waits for it to finish:
# 3. Start the Actor run and wait for it to complete
print("Starting Standvirtual extraction...")
run = client.actor("reventadata/standvirtual-scraper").call(run_input=run_input)
if run is None or run.status != "SUCCEEDED":
status = run.status if run else "unknown"
raise SystemExit(f"Run did not succeed (status: {status}).")
# 4. Fetch the resulting dataset items
dataset = client.dataset(run.default_dataset_id).list_items().items
print(f"Extraction complete! Retrieved {len(dataset)} listings.\n")
Step 3: Iterate and process dataset items
for item in dataset:
price = item.get("price")
km = item.get("mileageKm")
print(f"Listing: {item.get('title')} ({item.get('year')})")
if price is None:
print(" Price: not listed")
else:
print(f" Price: {price:,.0f} {item.get('currency')}")
print(f" Mileage: {km:,} km" if km is not None else " Mileage: not stated")
print(f" Power: {item.get('enginePowerCv')} cv, {item.get('gearbox')}")
print(f" Seller: {item.get('sellerType')} ({item.get('dealerName') or 'no dealer name'})")
print(f" Where: {item.get('city')}, {item.get('region')}")
print("-" * 50)
Step 4: Inspect a real row
Here is one row, a sample from a capture dated 2026-10-20, parsed with the Actor's own code. One field is left out of this excerpt: the engine capacity in cm3, 1984 for this car.
{
"id": "8097670190",
"url": "https://www.standvirtual.com/carros/anuncio/vw-golf-ver-2-0-tsi-opf-dsg-gti-ID8Q0ZWI.html",
"title": "VW Golf 2.0 TSI OPF DSG GTI",
"description": null,
"price": 31999.0,
"currency": "EUR",
"priceEvaluation": "BELOW",
"make": "VW",
"model": "Golf",
"version": "2.0 TSI OPF DSG GTI",
"year": 2023,
"mileageKm": 26157,
"fuelType": "Gasolina",
"gearbox": "Automática",
"enginePowerCv": 245,
"city": "Nogueira da Regedoura",
"region": "Aveiro",
"postedAt": "2026-10-09T14:32:16Z",
"imageUrl": "https://ireland.apollo.olxcdn.com/v1/files/siem67vm28sp-STDVTLPT/image;s=640x480",
"sellerType": "professional",
"dealerName": "FMaia Car",
"dealerUrl": "https://FMaiaCar.standvirtual.com",
"badges": [
"WARRANTY"
],
"categoryId": "29",
"matchedKeyword": "golf gti"
}
Step 5: Export the data
Apify datasets export as JSON, CSV, XML, Excel, HTML table, RSS or JSONL, from Apify Console or through the API.
Understanding your data
Field by field:
id,url,title: Standvirtual's listing id, the link without its query string, and the title.make,model,version: as the site displays them.price,currency: the asking price as a number, ornullwhen the listing states none; EUR in every sample row.priceEvaluation: Standvirtual's own price indicator, such asBELOW,INorABOVE.year,mileageKm,enginePowerCv, engine capacity in cm3: integers.fuelType,gearbox: in Portuguese (Gasolinais petrol).city,region,postedAt(ISO 8601 UTC),imageUrl.sellerType,dealerName,dealerUrl:professionalorprivate, and for dealers the public name and Standvirtual page.badges,categoryId(29 cars, 65 motorbikes),matchedKeyword.
What the 27 kept sample rows show: every row was petrol with a 1984 cm3 engine and priced in EUR; 25 came from dealers and 2 from private sellers; priceEvaluation was BELOW 12 times, IN 12, ABOVE 2 and NONE once; WARRANTY appeared on 26 rows. description was empty on all 32 rows of the page.
Working with the API
call() holds the connection until the run ends and returns the Run object. For longer runs or a job queue, client.actor("reventadata/standvirtual-scraper").start(run_input=run_input) returns as soon as the run is created; keep its id and read the run later. Either way, the dataset id is the run's default_dataset_id, and client.dataset(...).list_items().items returns the rows. list_items() makes one API call and may not return every item of a large dataset; iterate_items() makes as many calls as it needs to return them all.
Authentication is the API token from API & Integrations. Keep it in an environment variable, as the snippet does, and never in the code you commit.
For event-driven pipelines, add a webhook on the ACTOR.RUN.SUCCEEDED event. Apify then POSTs to your endpoint, and the payload's resource is the run details, which carries defaultDatasetId. Your handler reads the rows from that dataset without polling.
Error handling: the Actor ends a run that saves no rows FAILED when a page is blocked or cannot be read, so check run.status before reading the dataset, as the snippet does. A search that loads normally but matches nothing ends SUCCEEDED with an empty dataset and a status message. A make that is not a URL slug also ends the run FAILED before the first page is fetched, and a value outside a fixed list (category, fuelType, sortBy) is refused before the run starts: the call returns an API error and the Actor is not started.
Scheduling: save an input as a task and attach an Apify schedule. Schedules run Actors and tasks at times set by a cron expression.
Advanced usage patterns
1. Several searches in one run
searchQueries takes a list, and each term is its own search. {"searchQueries": ["golf gti", "golf r"], "maxItems": 300} runs both; matchedKeyword tells you which term found each row, and a listing found by both is saved once.
2. Browse a whole category
Leave searchQueries empty and the Actor browses the category with your filters. {"category": "motos", "maxItems": 200} reads the first 200 motorbike listings, newest first. Without a keyword, make goes into the search path itself, so {"make": "bmw", "maxPrice": 20000} is one filtered search on the site. The recon measured the filters on cars; filters on the motorbike category were not measured, so check the first rows before you rely on one there.
3. Make plus keyword
With a keyword, make is applied to the rows after fetching, because the Actor does not combine both in one search path. A "serie 3" search with make: "bmw" keeps only BMW rows from Standvirtual's fuzzy results.
4. Monitoring
Pair a schedule with a webhook on ACTOR.RUN.SUCCEEDED to load new rows, and one on ACTOR.RUN.FAILED to alert you. The failure webhook catches runs that saved no rows because a page was blocked or unreadable; a search that stopped matching anything ends SUCCEEDED with an empty dataset, so check the dataset item count or the status message for that. Use sortBy: "newest" (the default) and compare id between runs to spot new listings.
Troubleshooting guide
- Zero rows (status message "0 results for ..."): FAILED means a page was blocked or could not be read. SUCCEEDED with an empty dataset means the pages loaded normally and the filters were too narrow, the keyword matched nothing, or
requireKeywordMatchdropped every title. - Run FAILED on
make: the value may hold only plain letters, digits and hyphens, as in Standvirtual's URLs (mercedes-benz, notMercedes Benz). - A model you expected is missing: there is no model filter; put the model in the search term.
- Fewer distinct rows than pages × 32 with
relevance: Standvirtual reshuffles that order between pages. Usenewest,priceAscorpriceDescfor long runs. - A listing you can see on the site is missing: with
requireKeywordMatchon, a title without every search word is dropped. On the sample page that removed a 2017 245 cv car titled only "VW Golf". - Reading the log: the run logs
Rejected N: ...per reason, thenPushed N row(s).. From Python:client.log(run.id).get(). For help, use the Actor's Store page.
Best practices
- Filter on the site. Price, year, mileage and fuel are sent to Standvirtual, so you read fewer pages.
- Set
maxItemsandmaxPagesto what you need. The defaults are 1000 rows and 50 pages; usemaxPages: 1while you test. - Use
newestfor repeat runs: it pages cleanly, whilerelevancereshuffles between pages. - Copy the make slug from a Standvirtual URL.
- Sort by
yearandmileageKmbefore averaging to spot outliers. - Schedule, don't loop. A schedule reruns a saved task on a cron expression.
- Leave the proxy off. Turn one on only if you see request failures.
Pricing
For current pricing and details, see the Store page.
Conclusion and next steps
With Standvirtual Scraper and the Apify Python client, a Standvirtual search becomes a list of typed rows: price, year, mileage, power, district and seller type. Start with one page, check the fields, then schedule the search and compare datasets over time.
Try Standvirtual Scraper yourself and let me know what you build!
About the author: reventadata builds and maintains marketplace scrapers on the Apify Store.
Resources
About the author
- Hi, I'm the engineer behind ReventaData. I build pay-per-event Apify Actors that turn public marketplace, classifieds, jobs and real-estate sites into clean, reliable datasets. Here on Hashnode, I share practical tutorials on collecting structured web data with Python and Apify, and on putting it to work: price tracking, lead lists and market analysis. Explore our turnkey scrapers: https://apify.com/reventadata
Comments
Join the discussionNo comments yet. Be the first to comment.




