# Auction.com Property Scraper (`one-api/auction-com-property-scraper`) Actor

Scrape Auction.com (Ten-X) foreclosure, bank-owned (REO) and private-seller auction listings. Search by location, ZIP, coordinates, or URL, pull enriched property details with auction schedule, bids and comps, and browse the Real Estate Auction Calendar with per-event property lists.

- **URL**: https://apify.com/one-api/auction-com-property-scraper.md
- **Developed by:** [ONE API](https://apify.com/one-api) (community)
- **Categories:** Lead generation, Real estate
- **Stats:** 5 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 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.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Auction.com Property Scraper

Scrape **Auction.com (Ten-X)** — the largest US distressed-property marketplace. Foreclosure, bank-owned (REO) and private-seller auction listings, enriched property details, and the **Real Estate Auction Calendar** with per-event property lists.

### What it does

- **Property Details** — auto-detects each input as a listing ID (digits) or `auction.com` URL; returns the enriched record (auction schedule, starting/current bid, reserve status, occupancy, estimated-value range, photos, foreclosure financials, sold comps when available).
- **4 search modes** — by location name (city / county / state), ZIP, `lat,lng` coordinates, or Auction.com URL — or `nationwide` for no geo filter. Availability, buying type, property type, occupancy, price/beds/sqft and sort filters all apply.
- **Auction Calendar** — one row per upcoming auction EVENT (live courthouse foreclosure sales + online REO auctions), filterable by state, date window and buying type.
- **Event drill-down** — give an event code (`E-31309`) or venue ID: one event summary row (with all/available/removed property counts) plus one row per property in that event.
- **Location autocomplete** and **lookups** (supported states, filter vocabularies, seller info).

### Output

- **One flat dataset row per listing / event / suggestion** — sortable, filterable, CSV-exportable.
- Columns: `Mode`, `ID`, `Event Code`, `Address`, `City`, `State`, `County`, `Zip`, `Property Type`, `Asset Type`, `Occupancy`, `Status`, `Beds`, `Baths`, `Sqft`, `Year Built`, `Starting Bid`, `Current Bid`, `Estimated Value`, `Auction Start`, `Auction End`, `Cover Photo`, `Listing URL`.
- Full upstream JSON kept in the `Raw` column for power users.

### Inputs

- Each section is independent — fill only the ones you need.
- Multiple inputs per section: one per line.
- The ⚙️ Filters section applies to every search and to event drill-down property lists; `Buying type` also scopes the calendar (Foreclosure → live courthouse events, REO → online auctions).

### Pricing

- Pay per result: **$3 per 1,000 dataset items** — same rate on every Apify plan tier.
- Apify start fee: $0.00005 per run.

### Notes

- `Availability: Removed / Ended` switches to the closed bucket — useful for post-auction research.
- Buying type, property type and price/beds/sqft filters are applied over the first 250 matches per page scanned upstream; totals note when that cap is hit.
- A listing's `Starting Bid` falls back to the auction's published opening bid; `Current Bid` is the live highest bid (or winning bid on closed listings).

### Errors

- Failures land in the dataset as rows with `Mode = "ERROR"` and the upstream error message in `Address` — nothing is silently dropped.

# Actor input Schema

## `property_inputs` (type: `array`):

Auto-detects each entry: digits → `/details/byid`, an auction.com URL → `/details/byurl`. Each row = one enriched record (auction schedule, bids, estimated-value range, photos, foreclosure financials, sold comps).

## `search_inputs` (type: `array`):

Auto-detects each entry: city/county/state or ZIP → location search, `lat,lng` → coordinate search, an auction.com URL → URL search, `nationwide` → no geo filter. Filters below apply to every search.

## `autocomplete_inputs` (type: `array`):

Free-text location lookups via `/autocomplete`. One row per suggested city / county / ZIP / address.

## `fetch_calendar` (type: `boolean`):

Lists upcoming auction EVENTS (courthouse foreclosure sales + online REO auctions) via `/calendar`. One row per event, filtered by the date/state fields below.

## `calendar_state` (type: `string`):

Two-letter state code to scope the calendar (e.g. `TX`). Empty = all states.

## `calendar_date_from` (type: `string`):

`YYYY-MM-DD` lower bound. Empty = today (past events hidden).

## `calendar_date_to` (type: `string`):

`YYYY-MM-DD` upper bound. Empty = ~120 days out.

## `event_inputs` (type: `array`):

Drill into one auction event via `/calendar/event` (e.g. `E-31309` or a numeric venueId). Returns one event summary row plus one row per property in the event.

## `availability` (type: `string`):

Active = live auctions; Removed = the closed/ended bucket.

## `buyingType` (type: `string`):

Auction.com buying type. Also scopes the calendar (Foreclosure → live courthouse events, REO → online events).

## `propertyType` (type: `string`):

Structure type to keep.

## `occupancy` (type: `string`):

Occupancy at listing time — a key auction-property signal.

## `priceRange` (type: `string`):

Format: `min:50000,max:400000` — or just `min:…` / `max:…`.

## `bedsRange` (type: `string`):

Format: `min:2,max:4`.

## `sqftRange` (type: `string`):

Format: `min:1000,max:2500`.

## `sort` (type: `string`):

Order of search results.

## `limit` (type: `integer`):

Max listings (or calendar events) returned per input. Upstream caps a page at 250.

## `pages` (type: `integer`):

How many pages to fetch for each search input.

## `fetch_states` (type: `boolean`):

One row per US state via `/states`.

## `fetch_enums` (type: `boolean`):

One row per filter enum group via `/enums` (buying types, property types, sorts…).

## `fetch_sell` (type: `boolean`):

One informational row on how selling works on auction.com via `/sell`.

## Actor input object example

```json
{
  "property_inputs": [
    "2093283",
    "https://www.auction.com/details/10118-ekukpe-dr-dallas-tx-2093283"
  ],
  "search_inputs": [
    "Dallas, TX"
  ],
  "autocomplete_inputs": [],
  "fetch_calendar": false,
  "calendar_state": "",
  "calendar_date_from": "",
  "calendar_date_to": "",
  "event_inputs": [],
  "availability": "active",
  "buyingType": "",
  "propertyType": "",
  "occupancy": "",
  "priceRange": "",
  "bedsRange": "",
  "sqftRange": "",
  "sort": "auction_date",
  "limit": 50,
  "pages": 1,
  "fetch_states": false,
  "fetch_enums": false,
  "fetch_sell": false
}
```

# 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 '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "property_inputs": [
        "2093283",
        "https://www.auction.com/details/10118-ekukpe-dr-dallas-tx-2093283"
    ],
    "search_inputs": [
        "Dallas, TX"
    ],
    "autocomplete_inputs": [],
    "event_inputs": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("one-api/auction-com-property-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 '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "property_inputs": [
        "2093283",
        "https://www.auction.com/details/10118-ekukpe-dr-dallas-tx-2093283",
    ],
    "search_inputs": ["Dallas, TX"],
    "autocomplete_inputs": [],
    "event_inputs": [],
}

# Run the Actor and wait for it to finish
run = client.actor("one-api/auction-com-property-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 '{
  "property_inputs": [
    "2093283",
    "https://www.auction.com/details/10118-ekukpe-dr-dallas-tx-2093283"
  ],
  "search_inputs": [
    "Dallas, TX"
  ],
  "autocomplete_inputs": [],
  "event_inputs": []
}' |
apify call one-api/auction-com-property-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,one-api/auction-com-property-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 <APIFY_API_TOKEN>` 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/hzumLz1V0q1OjhU1E/builds/uT0T1x3HFhi2bATV2/openapi.json