01 / Collect
Original sources only
Every record is collected straight from the official government or court record that published it. We never resell an aggregator's feed, and we never source second-hand.
// original official records only
Original-source auction data · REST API
Original-source US property auction data, one API.
We collect foreclosure, tax, and sheriff-sale listings directly from the original official government and court records that publish them — never from aggregators — then normalize, deduplicate, and lifecycle-track every record behind a single REST endpoint.
Live contract · api.auctionscrapers.com/v1/openapi.json
GET /v1/listings/{id}
Sample listing · address on file
Illustrative record · fields shown as returned
foreclosure
scheduled
Sale datetime
2026-08-12 10:00
Record type
foreclosure
Status
scheduled
Opening bid
$248,500
Provenance verified · linked to its original official source
2
states live
(CT & OH)
(CT & OH)
50
states with sources mapped
130+
original sources in the registry
0
aggregators, ever
What it is
A data pipeline built for records that never sit still.
Auction records get postponed, canceled, and re-noticed constantly — often described differently across the several official records that touch the same sale. We turn that mess into one clean, stable record with a documented history.
02 / Resolve
Identity & deduplication
The same sale seen in more than one official record converges to a single listing — keyed on case, parcel, and the initiating event, so a tax sale and a mortgage foreclosure on one parcel stay distinct.
// case + parcel + record_type
03 / Track
Lifecycle history
Postponements, cancellations, upset periods, and final sales are captured as events. The listing shows current state; the full date-change chain is always reconstructable.
// scheduled → postponed → sold
04 / Attest
Provenance & snapshots
Each record carries a link back to its original official source and a last_verified_at timestamp. Raw snapshots are retained so any field is traceable to its origin.
// source_url · last_verified_at
05 / Heal
Self-healing collection
Official sites change layouts without warning. When a source breaks, the pipeline detects the drift and repairs itself — so coverage recovers without a fire drill for you.
// drift-detected · auto-repaired
06 / Report
Coverage transparency
We publish where we're live, where sources are mapped, and where a source is blocked or pending — so a gap in the data is visible and explained, never silently missing.
// /v1/coverage · /v1/sources
Coverage
Live in two states. Mapped in fifty.
We'd rather be honest about our footprint than inflate it. Connecticut and Ohio are live in production today; the registry already charts original sources across every state, and each new one comes online source by source.
Live in production
Sources mapped & pending
CT · OH
Live in production, collecting daily
50 states
Original sources charted in the registry
130+ sources
Original official records tracked nationwide
Why source-by-source? Every jurisdiction publishes differently. We onboard one original source at a time and verify it end-to-end before it counts as live — so “covered” always means real, current records, not a promise.
The API
One authenticated call. Clean, typed records.
A single REST surface with a published OpenAPI 3.1 contract. Metered API keys, cursor pagination, and rate-limit headers on every response — the boring parts done right.
Metered API keys
Bearer-token auth. Each key has a per-minute limit and a monthly quota, surfaced in response headers.
Cursor pagination
Opaque keyset cursors and an exact total — stable across pages even as data changes.
Search & reference
Filter listings by state, county, status, and record type, or full-text search addresses with ?q=. Reference data lives at /v1/counties, /v1/coverage, and /v1/sources.
OpenAPI contract
An OpenAPI 3.1 document is the single source of truth every client builds against. Read the spec →
curl -s https://api.auctionscrapers.com/v1/listings?state=CT&status=scheduled \ -H "Authorization: Bearer as_live_•••••••••••"
{
"data": [
{
"id": "a3f1c2e8-…",
"record_type": "foreclosure",
"status": "scheduled",
"state": "CT",
"county_name": "…",
"sale_datetime": "2026-08-12T10:00:00-04:00",
"address_raw": "… street address on file",
"opening_bid": 248500,
"source_url": "https://… original official source",
"last_verified_at": "2026-07-06T04:12:00Z"
}
],
"total": 1284,
"next_cursor": "eyJzIjoi…"
}
Trust
Built to be checkable, and to behave.
Property-auction data is public record, but sourcing it responsibly is a discipline. Here's how we keep the data honest and our footprint polite.
Original-source provenance
Every record links back to the original official source it came from, with the times it was first and last seen. If you need to verify a listing, the trail is right there.
Polite, compliant collection
Honest user-agent, no logins, no CAPTCHA bypass, no rate-limit evasion. If a source can't be collected within its terms, we skip it and find another original source — and mark the gap.
Per-listing disclaimer
Auction details change without notice. Records are informational, derived from public data, and carry a disclaimer — always verify with the official source before you act.
Courtesy name redaction
Completed cases can have a party's name redacted on our surfaces as a courtesy — the rest of the public record stays intact. We hide a name from search, we don't rewrite history.
Get started
Point one endpoint at the whole country's auction record.
Tell us what coverage you need and how you'll use it. We'll set you up with a metered key and the OpenAPI contract to build against.