Real Estate
Foreclosure & Auction Listing
/extract/jsonSchema for foreclosure and property auction listings.
Download the schemareal-estate/foreclosure-auction-listing.json
foreclosure-auction-listing.schema
// names marked ? are optional
address:string// Street address of the foreclosure property. Commonly found in: auction listing page, foreclosure notice, property header.
city:string// City of the foreclosure property. Commonly found in: auction listing page, property address section, notice header.
state:string// State of the foreclosure property. Commonly found in: auction listing page, property address section, notice header.
zip_code:string// ZIP code of the foreclosure property. Commonly found in: property address, foreclosure notice.
latitude?:number// Geographic latitude coordinate. Commonly found in: map embed data, JSON-LD structured data.
longitude?:number// Geographic longitude coordinate. Commonly found in: map embed data, JSON-LD structured data.
property_type?:string// Type of property (e.g., single_family, condo). Commonly found in: property details, foreclosure notice, public records.
bedrooms?:number// Number of bedrooms. Commonly found in: property details, listing specs, public records.
bathrooms?:number// Number of bathrooms. Commonly found in: property details, listing specs, public records.
sqft?:number// Total interior square footage. Commonly found in: property details, listing specs, public records.
foreclosure_stage:string// Current stage of the foreclosure process. Commonly found in: listing status badge, foreclosure stage indicator, property header. One of: pre_foreclosure, auction, reo, bank_owned, other.
auction_date?:string// Scheduled date of the auction. Commonly found in: auction details section, countdown timer, event date display.
minimum_bid?:number// Minimum bid required at auction. Commonly found in: auction details, bidding info section, price display.
opening_bid?:number// Opening bid for the auction. Commonly found in: auction details, bidding info section, price display.
estimated_value?:number// Estimated market value of the property. Commonly found in: property valuation section, estimated value display, AVM data.
lien_amount?:number// Total amount of the lien(s) on the property. Commonly found in: lien details section, foreclosure notice, legal documents.
property_condition?:string// Reported condition of the property. Commonly found in: property condition section, inspection notes, listing details. One of: unknown, poor, fair, good, other.
occupancy_status?:string// Whether the property is currently vacant or occupied. Commonly found in: property details, occupancy status field, listing notes. One of: vacant, occupied, other.
inspection_allowed?:boolean// Whether property inspection is allowed prior to auction. Commonly found in: auction terms section, inspection details, listing notes.
trustee_name?:string// Name of the trustee managing the foreclosure. Commonly found in: foreclosure notice, legal documents, trustee details section.
lender_name?:string// Name of the lender initiating the foreclosure. Commonly found in: foreclosure notice, lender details section, legal documents.
case_number?:string// Legal case or file number for the foreclosure. Commonly found in: foreclosure notice, legal documents, case reference field.
default_amount?:number// Amount the borrower has defaulted on. Commonly found in: foreclosure notice, default details, legal documents.
page_title?:string// Title of the source page. Tabstack auto-fills this from page metadata when left empty.
favicon?:string// Favicon URL of the source page. Tabstack auto-fills this from page metadata when left empty.
Try it live
A sample Foreclosure & Auction Listing document, generated from the schema. Edit it, or paste a real response, and see it checked against the schema instantly. It runs in your browser, nothing is sent anywhere.
your-output.json
validation
Valid, matches Foreclosure & Auction Listing
Every required field is present and each value matches its type. Extra fields are allowed. A field the page does not carry is not guaranteed to come back as null, so check values rather than only checking for null.
/extract/json
Copy-paste usage
The same call in TypeScript, Python, and curl. Point it at your own URL and go. The schema drives the response, so you get back the fields you asked for instead of a page to parse.
Features
- ✓Typed TypeScript and Python SDKs
- ✓One call, no parsing code and no second LLM pass
- ✓The same field names on every request, even when the page layout changes
foreclosure-auction-listing.ts
// curl -sfLO https://raw.githubusercontent.com/Mozilla-Ocho/tabstack-schemas/main/real-estate/foreclosure-auction-listing.json
import Tabstack from '@tabstack/sdk'
import schema from './foreclosure-auction-listing.json' with { type: 'json' }
const client = new Tabstack() // reads TABSTACK_API_KEY from the environment
try {
const data = await client.extract.json({
url: 'https://example.com/listing/123',
json_schema: schema,
effort: 'standard', // 'min' | 'standard' | 'max'
})
console.log(data)
} catch (err) {
console.error('Extraction failed:', err)
}Ship this schema in one call.
Pass a URL, get matching JSON back. Free to start, no extraction layer to maintain.