Troostwijk Auction Extractor

Search Troostwijk Auctions by keyword and get every matching lot back as structured data. Type in what you are looking for, run it, and you get titles, current bids, bid counts, closing times, locations, categories and image URLs in a table you can export.

There are no URLs to paste. A search term is all it takes.

What people use it for

• Track what similar machines, vehicles or equipment are actually selling for
• Watch a keyword across every European auction Troostwijk runs and export the results on a schedule
• Build price history for a brand or model over weeks of auctions
• Feed listing data into a comparison site, marketplace or internal dashboard
• Pull image galleries and full specifications for lots you care about

Input

Field	Type	Description
searchTerm	string	The keyword to search for. Required.
language	string	Language for lot titles and specification names. English by default.
countries	array	Country codes to limit results to, such as nl, be, de, pl. Empty means everywhere.
category	string	Optional top level category ID if you want to narrow the search.
includeDetails	boolean	Opens each lot page for the full image gallery, specifications, condition remarks and auction name. Slower, much richer.
maxItems	integer	How many lots to save per run. Default 100, maximum 1000.
requestTimeoutSecs	integer	Per-request timeout. Default 30 seconds.

{
    "searchTerm": "skoda karoq",
    "language": "en",
    "countries": ["nl"],
    "includeDetails": true,
    "maxItems": 100
}

Output

One record per lot. With includeDetails off you get the core listing fields:

{
    "lotId": "02fbf485-31e5-49cd-970e-3e9c0b1296c2",
    "lotNumber": "A1-44400-27",
    "lotTitle": "Skoda Scala 1.5 TSI Business Edition. 150hp 2019 (Original-NL), G-316-NZ",
    "lotUrl": "https://www.troostwijkauctions.com/en/l/skoda-scala-1-5-tsi-business-edition-150hp-2019-g-316-nz-A1-44400-27",
    "currentBid": 5000.0,
    "currency": "EUR",
    "bidsCount": 0,
    "biddingStatus": "BIDDING_OPEN",
    "startDate": "2026-07-31T14:00:00+00:00",
    "endDate": "2026-08-11T17:15:00+00:00",
    "city": "Milsbeek",
    "countryCode": "NL",
    "coordinates": "5.94861,51.725",
    "imageUrl": "https://media.tbauctions.com/image-media/9361ca87-.../file",
    "platform": "TWK",
    "searchTerm": "skoda karoq",
    "scrapedAt": "2026-08-09T12:00:00+00:00"
}

Turn includeDetails on and each record also carries:

Field	Description
images	Every photo on the lot page, in order
attributes	Specifications as name and value pairs, for example brand, model, mileage, fuel type, year
categories	Category path the lot sits under
remarks	Seller notes on condition, wear and included options
quantity, condition, followersCount	Lot metadata
auctionName, auctionNumber, auctionLotCount	The auction the lot belongs to

Notes

• Results are paginated automatically until maxItems is reached or the search runs out of lots.
• If one lot page fails, that record still gets saved with an error field and the run keeps going.
• Amounts are converted to normal currency units, so 5000.0 EUR means five thousand euros.
• Dates come back as ISO 8601 UTC timestamps, ready to sort or compare.

Running it on a schedule

Bids move right up to the closing deadline, so a single export goes stale fast. Put the actor on an Apify schedule and every run appends a fresh snapshot to your dataset. That is the setup you want if you are after price history rather than a one off export.