# TruckScout24 Scraper (`lowlanddata/truckscout24-scraper`) Actor TruckScout24 is Europe's leading marketplace for used trucks, trailers and buses, and the category pages hold more live listings than any export gives you. Rows give net and gross price, vehicle type, location and category. No trader identity collected. - **URL**: https://apify.com/lowlanddata/truckscout24-scraper.md - **Developed by:** [Lowland Data](https://apify.com/lowlanddata) (community) - **Categories:** E-commerce, Automation, Business - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $1.79 / 1,000 results This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README ## TruckScout24 Scraper — GDPR-safe commercial vehicle listings Extract listings from **truckscout24.com** — Europe's leading marketplace for used trucks, trailers, tractor units, buses and vans — as clean, structured JSON. Price (net and gross), vehicle type, location and category, ready for price research, fleet sourcing and data pipelines. **No trader personal data, ever.** Trader names and phone numbers never appear in the output — not as an option you have to remember to switch off, but by design. Contact happens through the site's own inquiry form, which this actor never touches. ### Quick start (30 seconds) 1. Browse [truckscout24.com](https://www.truckscout24.com), pick a vehicle category (e.g. Trucks → used), and paste its URL into **categoryUrls**. 2. Click **Start**. That's the whole minimum setup. 3. When the run finishes, open the dataset's **Overview** tab for a clean table, or **Export** it as CSV/Excel/JSON. Add more category URLs to sweep several at once — they share the same `maxItems` budget. Everything works on a daily Schedule. ### What you can build with it - **Fleet sourcing.** Pull every truck or trailer in a category with net/gross price, vehicle type and location, to shortlist what's actually on the market across Europe right now. - **Price benchmarking.** Compare `priceNetEurCents` across a category to see where a specific make or body type is actually trading, not listed. - **Regional supply tracking.** `countryCode` and `city` let you see where inventory of a given vehicle type is concentrated. - **Feed an AI agent clean data.** Every field is structured, predictable and free of personal data, so an assistant or pipeline can consume it directly — no scrubbing, no compliance review before you store it. ### What you get Each listing is one dataset item: ```json { "listingId": "22880795", "url": "https://www.truckscout24.com/tsp/ts-228-80-795", "vehicleType": "Car transporter", "title": "Volvo FH 500 4x2 + ROLFO TRUCK-TRANSPORTER (3 UNITS) ...", "priceNetEurCents": 11900000, "priceGrossEurCents": 14399000, "countryCode": "BE", "city": "Overpelt", "category": "Transportfahrzeuge & Nutzfahrzeuge", "imageUrl": "https://cdn.truckscout24.com/data/listing/img/vga/ts/73/06/22880795-01.jpg", "imageCount": 50 } ``` Field notes, so you know exactly what you are buying: - `priceGrossEurCents` is `null` when a listing shows only a net price — not every seller publishes a VAT-inclusive figure. - `title` is the seller's own free text; `vehicleType` is the site's own category label for the listing, read separately. - `city` is occasionally just a country name when the site has no finer location for a listing — an honest pass-through of what TruckScout24 itself displays, not invented. - `category` strips the site's internal numeric bucket prefix, keeping only the readable label. ### How much does it cost to scrape TruckScout24? $1.99 per 1,000 listings delivered, pay-as-you-go: no subscription, and you pay per result rather than per hour. A run that finds nothing still costs the $0.005 actor start. In plain dollars: - **100 listings ≈ $0.20** — a category spot-check. - **500 listings ≈ $1.00** — a solid market snapshot. - **A 2,000-listing crawl ≈ $4.00** — a full category, deduplicated. The price is all-inclusive: your runs' platform usage is covered by it, with no separate compute or proxy charges. Datacenter proxies are sufficient — no residential proxy surcharge needed. Free-plan runs are limited to a sample of 5 items, enough to evaluate the output format against your real category. ### Not technical? Let your AI assistant set it up Copy this into ChatGPT, Claude or any AI assistant, fill in the one line, and follow the conversation: ```text Help me set up the "TruckScout24 Scraper" actor on Apify (https://apify.com/lowlanddata/truckscout24-scraper). Guide me one step at a time. What I want to watch: [E.G. "used box trucks for sale in Belgium and the Netherlands"] Guide me to: 1. Browse truckscout24.com, find the matching category page, and propose its URL as categoryUrls (an array - more than one category can be swept at once), plus maxItems. 2. Explain that this actor reads category pages, not keyword search or sort filters, because TruckScout24's own sort and categoryId query parameters are excluded by its robots.txt. 3. Create a free Apify account (apify.com), open the actor page, paste the values into the Input form, and start a run. 4. Set up a daily Schedule in the Apify Console with the same input, plus an email or Slack integration so new listings reach me automatically. 5. Show me how to export results as CSV/Excel, or read them from the API if I code. 6. If the results are what I wanted, remind me at the end to leave a quick rating on the actor page, and to report anything broken or missing on its Issues tab. ``` ### Input | Field | Description | | -------------------- | --------------------------------------------------------------- | | `categoryUrls` | One or more TruckScout24 category page URLs (see below). | | `maxItems` | Stop after this many listings, shared across all category URLs. | | `proxyConfiguration` | Keep Apify proxy enabled. | A run needs at least one category URL; anything else fails readably with the reason in the run's status message. #### Finding a category URL TruckScout24's own sort order and `categoryId` filter query parameters are excluded by the site's `robots.txt`, so this actor reads plain category pages instead — the part of the site robots.txt leaves open. Browse [truckscout24.com](https://www.truckscout24.com), use the site's own vehicle-type menu to narrow down to what you want (e.g. Trucks → used → Box), and copy that page's URL into `categoryUrls`. Each category page already lists every current listing in it, so this reaches the same inventory a filtered search would have, without touching the disallowed query parameters. ### Use it from your code Run the actor and get items straight back with one HTTP call (fine for scoped runs up to ~5 minutes): ```bash curl "https://api.apify.com/v2/acts/lowlanddata~truckscout24-scraper/run-sync-get-dataset-items?token=" \ -X POST -H "Content-Type: application/json" \ -d '{"categoryUrls": ["https://www.truckscout24.com/trucks/used"], "maxItems": 100}' ``` Node.js: ```js import { ApifyClient } from 'apify-client'; const client = new ApifyClient({ token: '' }); const run = await client.actor('lowlanddata/truckscout24-scraper').call({ categoryUrls: ['https://www.truckscout24.com/trucks/used'], maxItems: 100, }); const { items } = await client.dataset(run.defaultDatasetId).listItems(); ``` Python: ```python from apify_client import ApifyClient client = ApifyClient("") run = client.actor("lowlanddata/truckscout24-scraper").call( run_input={"categoryUrls": ["https://www.truckscout24.com/trucks/used"], "maxItems": 100}) items = client.dataset(run["defaultDatasetId"]).list_items().items ``` For large crawls, start the run asynchronously and fetch the dataset when the finished-run webhook fires. Schedules (e.g. a daily category snapshot), webhooks and the Make/Zapier/n8n integrations all work out of the box — this is a standard Apify actor. ### Use it with AI agents (MCP) Claude, Cursor and other MCP-capable agents can run this scraper as a tool through Apify's hosted MCP server: the agent fills in the category itself, starts the run and reads the results — no glue code. Claude Code: ```bash claude mcp add apify --transport http "https://mcp.apify.com?actors=lowlanddata/truckscout24-scraper" ``` Cursor or Claude Desktop (add a custom connector / MCP server with this URL): ```text https://mcp.apify.com?actors=lowlanddata/truckscout24-scraper ``` Sign in with your Apify account when prompted — runs are billed to it. Setup details per client: [Apify MCP docs](https://docs.apify.com/platform/integrations/mcp), or start from this actor's own MCP page: [apify.com/lowlanddata/truckscout24-scraper/api/mcp](https://apify.com/lowlanddata/truckscout24-scraper/api/mcp). Prompts that work once connected: - "Pull every box truck listing on TruckScout24 and tell me the median net price." - "Snapshot the trailer category and group listings by country." - "Watch this category daily and tell me when a new listing under €30,000 net appears." ### Beyond the result window TruckScout24 pages 25 listings at a time; this actor pages through automatically up to `maxItems`, deduplicating by `listingId`. There is no hard cap beyond `maxItems` itself. ### Is it legal to scrape TruckScout24? Public listing data — price, vehicle type, location, category — is public commercial information, and this scraper is built so that the hard part of the question never arises: **no personal data enters your dataset in the first place.** This actor only reads category pages, which TruckScout24's `robots.txt` leaves open; its sort order and category-filter query parameters are explicitly excluded by that same file and are never requested. Requests are paced, run through standard datacenter proxies, and nothing here works around any access control. One honest limit: listing titles are the seller's own words, delivered as-is. ### Is there a TruckScout24 API alternative? TruckScout24 publishes no public API for listings. This actor is the practical alternative: the same listings as structured JSON through one HTTP call (`run-sync-get-dataset-items`), on a schedule, or as an MCP tool for AI agents — with the GDPR question already answered in the data itself. ### Does TruckScout24 block scrapers? Category pages serve their data openly to a plain request — and this actor stays inside that welcome: paced requests, standard datacenter proxies, load kept negligible. No CAPTCHA fights, no bot-wall cat-and-mouse — which is also why runs are fast and reliable enough for daily schedules. ### How do I monitor TruckScout24 prices? Add a daily Schedule in the Apify Console with your category URL(s) and an email/Slack integration on the runs — every listing's price and specs land in your inbox, so a new arrival or a price shift in a watched category is visible the next morning. ### FAQ **Can I get trader names or phone numbers?** No — by design. That is the product: data you can store, share and process without a GDPR review. **Why category URLs instead of a keyword search?** TruckScout24's `robots.txt` explicitly excludes its sort order and category-filter query parameters. Category pages are not excluded and already list every current listing in that category, so this actor uses them instead of working around the disallowed paths. **How fresh is the data?** Live at run time — every run queries TruckScout24 directly. For continuous freshness, schedule the actor. **Can I export to Excel or CSV?** Yes — every dataset exports as CSV, Excel, JSON or XML from the Apify Console or API. **What happens on a very large category?** The actor pages through automatically, deduplicating by `listingId`, until either the category is exhausted or `maxItems` is reached — raise `maxItems` to see more of a big category. **Does it work with Make, Zapier or n8n?** Yes — it is a standard Apify actor; all platform integrations, webhooks and schedules apply. ### Related scrapers Working European or industrial B2B data? The same GDPR-clean guarantee, same output shape: - [Troostwijk Auctions Scraper](https://apify.com/lowlanddata/troostwijk-scraper) — European industrial and agricultural equipment auctions. - [Mascus Scraper](https://apify.com/lowlanddata/mascus-scraper) — used agricultural, construction and material-handling equipment for sale worldwide. ### Troubleshooting The actor fails fast with the reason in the run's status message: - **"Not a TruckScout24 category URL."** — `categoryUrls` entries must be full `https://www.truckscout24.com//used...` category page URLs, not a search link or a single listing page. - **Fewer items than requested on a free plan** — the 5-item free sample cap; run on a paid Apify plan for full results. ### Support Found an issue or missing a field you need? Open an issue on the actor's **Issues tab** — reports get fixed, this actor is actively maintained. Working well for you? A **rating on this page** takes ten seconds and helps other buyers find a GDPR-clean option among the lookalikes — it is also the clearest signal of what we should build next. # Actor input Schema ## `categoryUrls` (type: `array`): One or more TruckScout24 category page URLs to sweep, e.g. https://www.truckscout24.com/trucks/used. Browse truckscout24.com, pick a vehicle category, and paste its URL here - the site's own sort and category filters are not used by this actor (see "Finding a category URL" below for why). ## `maxItems` (type: `integer`): Stop after this many listings, across all category URLs combined. Free-plan runs are capped at 5 items. The form starts at 25 for a cheap first run - that is the form's prefill, not a cap on your plan; clear it to use the default of 500. ## `proxyConfiguration` (type: `object`): Proxy settings. Keep Apify proxy enabled. ## `reportFailures` (type: `boolean`): When a run fails, send the developer the actor name and build, an error category, the error message (truncated) and a one-way hash of your input - so a bug can be fixed without anyone asking you to reproduce it. Your input itself, your results and your identity are never sent, and successful runs send nothing at all. Switch this off and the actor behaves exactly the same. ## Actor input object example ```json { "categoryUrls": [ "https://www.truckscout24.com/trucks/used" ], "maxItems": 25, "proxyConfiguration": { "useApifyProxy": true }, "reportFailures": true } ``` # Actor output Schema ## `listings` (type: `string`): Scraped TruckScout24 listings, one JSON object per listing. # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "categoryUrls": [ "https://www.truckscout24.com/trucks/used" ], "maxItems": 25, "proxyConfiguration": { "useApifyProxy": true } }; // Run the Actor and wait for it to finish const run = await client.actor("lowlanddata/truckscout24-scraper").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "categoryUrls": ["https://www.truckscout24.com/trucks/used"], "maxItems": 25, "proxyConfiguration": { "useApifyProxy": True }, } # Run the Actor and wait for it to finish run = client.actor("lowlanddata/truckscout24-scraper").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "categoryUrls": [ "https://www.truckscout24.com/trucks/used" ], "maxItems": 25, "proxyConfiguration": { "useApifyProxy": true } }' | apify call lowlanddata/truckscout24-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,lowlanddata/truckscout24-scraper" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/rI0V5ryRGu1Cghfed/builds/TcC53dsGWcfXl3N86/openapi.json