Auction.com Scraper | $1 / 1k | Fast & Reliable avatar

Auction.com Scraper | $1 / 1k | Fast & Reliable

Pricing

$1.00 / 1,000 results

Go to Apify Store
Auction.com Scraper | $1 / 1k | Fast & Reliable

Auction.com Scraper | $1 / 1k | Fast & Reliable

Scrape Auction.com real estate auctions into clean, structured listings. Get auction dates/status, price signals, occupancy/asset type, beds/baths, sqft, addresses, photos and more. Ideal for inventory tracking, deal sourcing and pricing trend analysis.

Pricing

$1.00 / 1,000 results

Rating

0.0

(0)

Developer

Fatih Tahta

Fatih Tahta

Maintained by Community

Actor stats

1

Bookmarked

20

Total users

4

Monthly active users

2 hours ago

Last modified

Share

Auction.com Scraper

Slug: fatihtahta/auction-com-scraper

Overview

Auction.com Scraper collects structured property auction listing data, including listing identifiers, location details, pricing signals, auction timing, and key property attributes. It captures listing metadata, property summaries, and media links in a consistent JSON format suitable for analysis or enrichment. Auction.com is a public marketplace for real estate auctions, making it valuable for tracking inventory, pricing movements, and market activity. Runs are automated and consistent, saving time compared to manual collection and ensuring repeatable datasets for workflows.

Why Use This Actor

  • Market research / analytics: Build datasets for auction inventory, pricing trends, and regional activity over time.
  • Product & content teams: Populate listings, market summaries, and location pages with up-to-date auction data.
  • Developers / data engineering pipelines: Feed BI tools, ETL jobs, or internal dashboards with structured records.
  • Lead gen / enrichment: Identify properties, locations, and asset attributes to enrich CRM or prospecting data.
  • Monitoring / competitive tracking: Track new auctions, status changes, and timing shifts across markets.

Input Parameters

Provide any combination of URLs, queries, and filters. Leave optional fields empty to collect broader results.

ParameterTypeDescriptionDefault
startUrlsstring[]One or more Auction.com search result pages, category pages, or listing URLs to collect.
limitintegerMaximum number of listings to save per query. Set lower for quick sampling or higher for deeper coverage.50000

Example Input

{
"startUrls": [
"https://www.auction.com/residential/26.361645418238187,-129.1526449272487,47.2563363379616,-102.5217855522487_bounds/active_lt/auction_date_order,resi_sort_v2_st/y_nbs",
"https://www.auction.com/details/1-plymouth-cir-pueblo-co-1876508"
],
"limit": 2000
}

Output

6.1 Output destination

The actor writes results to an Apify dataset as normalized JSON records. The dataset is designed for direct consumption by analytics tools, ETL pipelines, and downstream APIs without post-processing.

6.2 Record identifiers (all listing items)

Every listing record includes stable identifiers at the top level and in source_context.external_ids:

  • record_type (string, required): property_listing for normal listing records.
  • record_id (string, required): Auction.com listing ID when available.
  • source_context.listing_url (string, optional): Canonical listing URL.
  • entity.title (string, required): Human-readable listing title.

Recommended idempotency key: record_id

Use source_context.listing_url as a secondary audit and deduplication key when joining records across runs.

6.3 Examples

Example: listing

{
"record_type": "property_listing",
"record_id": "2029773",
"source_context": {
"source_name": "Auction.com",
"source_domain": "auction.com",
"source_url": "https://www.auction.com/residential/26.361645418238187,-129.1526449272487,47.2563363379616,-102.5217855522487_bounds/active_lt/auction_date_order,resi_sort_v2_st/y_nbs",
"listing_url": "https://www.auction.com/details/8316-w-jayne-crest-st-magna-ut-2029773",
"canonical_url": "https://www.auction.com/details/8316-w-jayne-crest-st-magna-ut-2029773",
"seed_type": "url",
"seed_value": "https://www.auction.com/residential/26.361645418238187,-129.1526449272487,47.2563363379616,-102.5217855522487_bounds/active_lt/auction_date_order,resi_sort_v2_st/y_nbs",
"external_ids": {
"listing_id": "2029773",
"urn": "adc:listing:2029773",
"property_id": "1407688"
}
},
"entity": {
"title": "8316 W Jayne Crest St, Magna, UT 84044, Salt Lake County",
"url": "https://www.auction.com/details/8316-w-jayne-crest-st-magna-ut-2029773",
"status": "SALE_PENDING",
"external_ids": {
"listing_id": "2029773",
"urn": "adc:listing:2029773",
"property_id": "1407688"
}
},
"listing": {
"listing_id": "2029773",
"listing_type": "TRUSTEE",
"deal_type": "auction",
"listing_status": "SALE_PENDING",
"listing_status_group": "ACTIVE",
"listing_status_label": "Jun 08",
"is_new_listing": false,
"auction": {
"start_date": "2026-06-08T07:00:00Z",
"visible_auction_start_date_time": "2026-06-08T16:00:00Z",
"is_online": false,
"venue_type": "LIVE",
"event_code": "E-31352A",
"trustee_sale": true
}
},
"pricing": {
"seller_current_value": 350000,
"estimated_value": 338809,
"currency": "USD"
},
"location": {
"address": "8316 W JAYNE CREST ST",
"full_address": "8316 W Jayne Crest St, Magna, UT 84044, Salt Lake County",
"street": "8316 W JAYNE CREST ST",
"city": "MAGNA",
"county": "Salt Lake",
"state": "UT",
"postal_code": "84044",
"country": "United States",
"country_code": "US",
"latitude": 40.705287,
"longitude": -112.089701,
"coordinates": {
"latitude": 40.705287,
"longitude": -112.089701
}
},
"property": {
"property_id": "1407688",
"property_type": "SINGLE_FAMILY",
"property_subtype": "SINGLE_FAMILY_HOME",
"bedrooms": 3,
"bathrooms": 2,
"floor_area": 1104,
"floor_area_sqft": 1104,
"lot_area": 0.17,
"year_built": 2022,
"property_taxonomy": {
"structure_type_code": "SINGLE_FAMILY_HOME",
"structure_type_group": "SINGLE_FAMILY"
}
},
"availability": {
"occupancy_status": "OCCUPIED"
},
"media": {
"main_image_url": "https://adc-tenbox-prod.imgix.net/resi/propertyImages/1407688/4620256ord00815111_1.v1.jpeg?auto=compress,format",
"image_urls": [
"https://adc-tenbox-prod.imgix.net/resi/propertyImages/1407688/4620256ord00815111_1.v1.jpeg?auto=compress,format"
]
},
"attributes": {
"tags": [
"RURL"
],
"auction_terms": {
"product_type": "TRUSTEE",
"asset_type": "FORECLOSURE",
"is_reserve_displayed": true,
"buyer_premium_available": false,
"is_direct_offer_enabled": false
},
"source_specific": {
"attribution_source": "AUCTION_COM",
"venue_type": "LIVE",
"event_code": "E-31352A",
"trustee_sale": true
}
}
}

Field reference

Listing fields

  • record_type (string, required): Record discriminator, usually property_listing.
  • record_id (string, required): Stable source listing identifier.
  • source_context (object, required): Source name/domain, source URL, listing URL, seed context, and external IDs.
  • entity (object, required): Display title, listing URL, current status, and source IDs.
  • listing (object, optional): Listing ID, auction deal type, listing status labels, new-listing flag, and auction schedule/event details.
  • pricing (object, optional): Reserve price, starting bid, seller current value, source valuation, and currency when available.
  • location (object, optional): Address components, postal code, county/state, country, and coordinates.
  • property (object, optional): Property ID, type/subtype, beds, baths, floor area, lot size, year built, and source taxonomy.
  • availability (object, optional): Occupancy or availability status when provided.
  • media (object, optional): Main image URL, image URL array, and source photo count.
  • attributes (object, optional): Marketing tags, hot-listing flags, auction terms, source-specific attribution, venue, event, and trustee-sale values.

Data guarantees & handling

  • Best-effort extraction: fields may vary by region/session/availability/UI experiments.
  • Optional fields: null-check in downstream code.
  • Deduplication: recommend Metadata.Listing URL.

How to Run on Apify

  1. Open the Actor in Apify Console.
  2. Configure your search parameters (e.g., category/practice area, state/region, optional city).
  3. Set the maximum number of outputs to collect.
  4. Click Start and wait for the run to finish.
  5. Download results in JSON, CSV, Excel, or other supported formats.

Scheduling & Automation

Scheduling

Automated Data Collection

Schedule runs to keep your dataset fresh and monitor changes over time.

  • Navigate to Schedules in Apify Console
  • Create a new schedule (daily, weekly, or custom cron)
  • Configure input parameters
  • Enable notifications for run completion
  • (Optional) Add webhooks for automated processing

Integration Options

  • Webhooks: Trigger downstream actions when a run completes
  • Zapier: Connect to 5,000+ apps without coding
  • Make (Integromat): Build multi-step automation workflows
  • Google Sheets: Export results to a spreadsheet
  • Slack/Discord: Receive notifications and summaries
  • Email: Send automated reports via email

Performance

Estimated run times:

  • Small runs (< 1,000 outputs): ~2–3 minutes
  • Medium runs (1,000–5,000 outputs): ~5–15 minutes
  • Large runs (5,000+ outputs): ~15–30 minutes

Execution time varies based on filters, result volume, and how much information is returned per record.

Compliance & Ethics

Responsible Data Collection

This actor collects publicly available real estate auction listing information from {{TARGET_SITE}} for legitimate business purposes, including:

  • Real estate research and market analysis
  • Investment scouting and property research
  • Portfolio monitoring and valuation review

This section is informational and not legal advice.

Best Practices

  • Use collected data in accordance with applicable laws, regulations, and the target site’s terms
  • Respect individual privacy and personal information
  • Use data responsibly and avoid disruptive or excessive collection
  • Do not use this actor for spamming, harassment, or other harmful purposes
  • Follow relevant data protection requirements where applicable (e.g., GDPR, CCPA)

Support

For help or questions, open an issue or use the actor page on Apify. Please include the input you used (redacted if needed), the run ID, a clear expected vs. actual description, and an optional small output sample to speed up troubleshooting.