AuctionTime Scraper

AuctionTime Scraper returns public AuctionTime.com equipment auction listings (farm machinery, construction equipment, trucks, trailers and attachments) as structured records: listing ID and URL, title, category, current bid, sale end time, year, hours, location, seller and photo URLs. Paste one or more public AuctionTime search, category or listing URLs and get a clean dataset back.

The Actor uses a bounded browser session with an owner-managed residential access route that exits in the listing site's country. It deduplicates by listing ID, validates every record before writing, and reports anti-bot challenges honestly. It does not log in, bid, access watchlists, or perform account actions.

Input

{
  "searchUrls": [{ "url": "https://www.auctiontime.com/listings/upcoming-auctions/construction-equipment/4" }],
  "maxItems": 25,
  "enrichDetails": true,
  "maxDetailPages": 10
}

• searchUrls: public AuctionTime search, category or listing URLs. To filter by keyword, manufacturer or state, run the search on auctiontime.com and paste the resulting URL. Each search URL is read from its first results page (about 25–30 listings). Empty input uses the tractors category. Older saved inputs that still send searchQuery, listingType, category, manufacturer or state are accepted, but those fields are ignored and listed in SUMMARY.warnings.
• maxItems: hard cap on saved and charged listings (1–500).
• enrichDetails and maxDetailPages: the first maxDetailPages listings are opened for bid, sale-end, location and seller details. Further listings are saved from their search card (title, category, location, photo) without a detail visit.

Output

Each dataset row includes listing ID and URL, title, category, sale end time (auctionDate), current bid (price, priceDisplay), year, hours, location, seller, image URLs, source URL and scrape timestamp. make and model are null because AuctionTime does not show them as separate fields; they appear inside title. A SUMMARY key-value record holds counts, the stop reason, charged events and warnings.

Pricing

This Actor uses pay-per-event pricing. Live Apify Store event prices (USD):

Event	FREE	BRONZE	SILVER	GOLD / PLATINUM / DIAMOND	When it is charged
listing-scraped	$0.050001	$0.04875	$0.0475	$0.04	Once for each unique validated listing written to the dataset
apify-actor-start	$0.086929	$0.084755	$0.082582	$0.069543	Once per run per GB of memory (default 1 GB)

Example on the FREE tier: 25 listings cost about $1.25 in result events plus one start event. Listings that are not saved, duplicates, and blocked pages are never charged. Apify platform usage for the run is included in these prices.

Limitations

AuctionTime may challenge automated traffic or change its page markup. The Actor detects challenge pages and ends as failed, with no result charges, when every supplied page is blocked. Pagination beyond the first results page of each URL is not followed; add more URLs to cover more listings. The run stops cleanly before its timeout and keeps the listings saved so far. It is intended for public-data research and automation; confirm compliance with AuctionTime terms and applicable law.

What data does AuctionTime Scraper return?

Field	Type	Description
listingId	string	Listing ID
listingUrl	string	Listing URL
title	string or null	Title
category	string or null	Category
auctionDate	string or null	Auction Date
price	number or null	Current Price
priceDisplay	string or null	Displayed Price
year	integer or null	Year
make	string or null	Make
model	string or null	Model
hours	number or null	Hours
location	string or null	Location
seller	string or null	Seller
imageUrls	array	Images
sourceUrl	string	Source URL
scrapedAt	string	Scraped At

Use cases

• Schedule repeatable collection and export results to downstream workflows.
• Run a one-off research job and export the structured result as JSON, CSV, Excel, XML, or RSS from Apify.
• Schedule the same input to monitor changes over time and send completed datasets to a webhook or integration.
• Feed schema-shaped records into a database, spreadsheet, BI tool, or AI workflow with the source URL retained for verification.

Run AuctionTime Scraper with the Apify API

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('muhammadafzal/auctiontime-scraper').call({
  "searchUrls": [
    {
      "url": "https://www.auctiontime.com/listings/upcoming-auctions/tractors/1100"
    }
  ],
  "maxItems": 25
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

You can also run the Actor from Apify Console, schedules, webhooks, the REST API, Make, Zapier, n8n, or the hosted Apify MCP server.

Support

When reporting a problem, include the Actor run ID, a redacted input, the expected result, and a small public example URL when applicable. Do not post API tokens, cookies, credentials, or personal data in an issue.

Frequently asked questions

Can I schedule AuctionTime Scraper?

Yes. Use an Apify schedule to run the same saved input at a chosen interval, then connect a webhook or integration to process the dataset when the run finishes.

How do I filter by keyword, manufacturer or state?

Run the search on auctiontime.com with the filters you need, copy the results URL, and paste it into searchUrls.

How should I test a new input?

Begin with the prefilled example or a small limit. Confirm that the output fields, source coverage, runtime, and live charges match your workflow before increasing the scope.

How do I export the results?

Open the run's default dataset in Apify Console and export JSON, CSV, Excel, XML, or RSS. Applications can retrieve the same records through the Apify API client or REST dataset endpoint.

Can an AI agent call this Actor?

Yes. Add muhammadafzal/auctiontime-scraper through the hosted Apify MCP server or call it through the API. The Actor's input and dataset schemas help agents construct valid requests and interpret returned records.

Recommended workflow

1. Define the smallest useful scope. Choose a representative public URL, query, identifier, or filter and keep the first result limit low.
2. Run and inspect. Check the run log, dataset item count, field coverage, source URLs, and live event or usage charges.
3. Validate downstream assumptions. Confirm nullable fields, deduplication keys, timestamps, and any locale-specific formats before importing records into another system.
4. Scale gradually. Increase limits or scheduling frequency only after the small run behaves as expected. Use Apify's maximum-cost and timeout controls to bound large jobs.
5. Monitor changes. Keep a small known-good input as a canary. If the source layout or API changes, compare the new dataset with a previously validated run and report the run ID when requesting support.

For recurring workflows, store the exact Actor input with your pipeline configuration. This makes runs reproducible and helps distinguish a source-data change from an input change.

Last verified: 2026-10-27