# Xome Foreclosure & Auction Property Scraper (`jongoose/xome-scraper`) Actor

Scrape Xome foreclosure & auction listings - address, geo, opening/starting bid, buy-it-now, reserve, beds/baths, sqft, property type, foreclosure stage (bank-owned, short sale, 2nd-chance), auction date & photo. By state, city, ZIP or URL; nationwide if blank.

- **URL**: https://apify.com/jongoose/xome-scraper.md
- **Developed by:** [James Scott](https://apify.com/jongoose) (community)
- **Categories:** Real estate, Lead generation
- **Features:** Limited permissions
- **Stats:** 22 total users, 7 monthly users, 85.5% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.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?

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

## Xome Foreclosure & Auction Property Scraper

Scrape **foreclosure and auction real-estate listings from [Xome](https://www.xome.com/auctions)** into clean, structured data - no Xome account or API key required.

Xome auctions bank-owned homes, foreclosures, short sales and second-chance (CWCOT) properties nationwide. This actor pulls the full listing feed by **state, city, ZIP, or URL** - ideal for foreclosure investors, real-estate wholesalers, and market analysts.

### What you get (per listing)

- **Full address** - street, city, state, ZIP + **latitude / longitude**
- **Pricing** - headline bid with its label (Est. Opening Bid / Starting Bid / High Bid / Final Bid), plus **starting bid, buy-it-now price and reserve** when set
- **Foreclosure stage** - Foreclosure, Bank Owned, Short Sale, 2nd-Chance Foreclosure, Non-Bank Owned
- **Auction details** - status (Active / Coming Soon / Finished), auction **start & end date**, event name, and auction type (In-Person / Online)
- Beds, baths, square footage, year built, property type (Single Family, Multi-Family, Condo, Townhouse, Mobile/Manufactured, Land, Commercial...)
- **Primary photo** URL and the canonical **listing URL**

### Input

Pick **any one** way to target listings:

- **Xome auction URLs** - paste state or city listing pages, e.g. `https://www.xome.com/auctions/listing/TX` or `https://www.xome.com/auctions/listing/TX/Dallas`.
- **State** - a two-letter code (e.g. `TX`) returns every auction/foreclosure in that state.
- **City + State** - narrow to one city (e.g. City `Dallas` + State `TX`).
- **ZIP** - narrow to a single ZIP (e.g. `75201`).
- Leave everything blank and the actor **sweeps all 50 states** until `maxItems` is reached.

**Max listings** caps the run.

#### Example input

```json
{ "startUrls": [{ "url": "https://www.xome.com/auctions/listing/TX" }], "maxItems": 500 }
```

```json
{ "state": "FL", "maxItems": 1000 }
```

### Why this actor

- **Direct from Xome's own listing API** - every field is read straight from the same JSON feed the site itself renders, so records are complete and there are **no slow per-listing detail requests**.
- **Fast + cheap** - runs on Apify's default **datacenter proxy** (the API is key-gated, not IP-gated), so no pricey residential proxy is needed.
- **Foreclosure-grade fields** - opening bid, auction date and foreclosure stage that generic real-estate scrapers don't surface.
- Export as JSON, CSV, Excel, or pull via the API.

### Notes & limitations

- **Estimated value** and **lot size** are not exposed on Xome's search feed (they appear only on the per-property detail page), so they are returned as `null`.
- Bid amounts of `$0` on foreclosures mean the **opening bid is "to be determined"** - surfaced as `price: null` with the label preserved.
- This data is for market research and lead generation; it is **not a consumer report** and must not be used for FCRA-covered purposes.

# Actor input Schema

## `startUrls` (type: `array`):

One or more Xome auction listing URLs, e.g. https://www.xome.com/auctions/listing/TX (a state) or https://www.xome.com/auctions/listing/TX/Dallas (a city). The state / city is read from the URL path. If left empty, the State / City / ZIP fields below are used.

## `state` (type: `string`):

Two-letter state code to scrape when no Start URL is given (e.g. "TX", "CA", "FL"). Returns every Xome auction / foreclosure listing in that state.

## `city` (type: `string`):

Narrow the search to a single city. Requires State to be set too (e.g. City "Dallas" + State "TX").

## `zip` (type: `string`):

Narrow the search to a ZIP code (e.g. "75201"). Requires State to be set too (Xome's ZIP pages live under the state) and returns Xome's own nearby-area results for that ZIP, exactly as the site shows them. Note: many ZIPs have no active auctions.

## `maxItems` (type: `integer`):

Stop after collecting this many listings (across all locations). If no location is given at all, the actor sweeps every US state until this cap is reached.

## `proxyConfiguration` (type: `object`):

Xome's listing API is gated only by a public key (not by IP), so it works fine through Apify's default datacenter proxy - no residential proxy needed.

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://www.xome.com/auctions/listing/TX"
    }
  ],
  "state": "TX",
  "maxItems": 100,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# 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 = {
    "startUrls": [
        {
            "url": "https://www.xome.com/auctions/listing/TX"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("jongoose/xome-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 = { "startUrls": [{ "url": "https://www.xome.com/auctions/listing/TX" }] }

# Run the Actor and wait for it to finish
run = client.actor("jongoose/xome-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 '{
  "startUrls": [
    {
      "url": "https://www.xome.com/auctions/listing/TX"
    }
  ]
}' |
apify call jongoose/xome-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jongoose/xome-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/cVP6T8lrMtdlszYFX/builds/lRKXjm9FGY1XfQjNt/openapi.json