> ## Documentation Index
> Fetch the complete documentation index at: https://docs.realie.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Property Data Schema (v3)
> The full nested v3 parcel record — the standard response shape and the bulk export shape
This page documents the **full nested v3 parcel record** — the shape shipped in bulk full-record exports. Fields with no value for a parcel are omitted rather than returned as null. Persist `realieParcelId` as your property key: API responses in the v3 shape carry no `_id` at all, and the `_id` values in bulk files and flat responses are regenerated on each data load — never a stable reference.
Normalized coded fields store values from the **Realie code system** (`XX####` codes plus integer ordinal/band scales); every such code decodes with the [Property Feature Field Key](/api-reference/v3/feature-key), which also documents the system's three representation classes and its append-only guarantee. The deliberate exception is the jurisdiction-issued fields documented below (`stateLandUseCode`, `countyLandUseCode`, `taxDistrictCode`, `zoningInfo.zoningCode`) — those carry each jurisdiction's own value verbatim, with no national decode table.
API endpoints return this nested record for accounts with the **v3 response shape enabled** — the default for new accounts; existing accounts enable it from the dashboard's **Usage** page (one-way, see the [migration FAQ](/api-reference/v3/migration-faq)). Accounts that haven't switched receive the same data in the **v2-compatible flat layout** documented in the [legacy tab](/api-reference/property-data-schema); the [migration guide](/api-reference/v3/migration) includes a field-by-field mapping between the two shapes. Two current exceptions return the flat layout even on v3-enabled accounts — records resolved through legacy coverage fallbacks, and searches using foreclosure filters (see the [migration FAQ](/api-reference/v3/migration-faq)).
## Identity & location
Primary parcel identifier (Assessor's Parcel Number / tax map parcel ID) as recorded by the county assessor. Example: "0314- -0009"
Stable Realie parcel identifier, persistent across data releases — persist this as your property key. Format: 5-digit county FIPS + the parcel ID with spaces escaped as `~`. Example: "11001-0314-\~-0009"
Two-letter USPS state abbreviation for the parcel. Example: "DC"
Street number and street name of the property, promoted from `propertyLocation.address`. Example: "1217 12TH ST NW"
Property use code, promoted from `propertyClassification.propertyUseCode`. Coded value — decode with the [Property Feature Field Key](/api-reference/v3/feature-key). Example: "1110"
5-digit ZIP code of the property, promoted from `propertyLocation.zipCode`. Example: "20005"
5-digit FIPS code (state + county) of the parcel's county, promoted from `propertyLocation.fipsCode`. Example: "11001"
Latitude of the parcel centroid in decimal degrees (mirrors `coordinates.latitude`). Omitted when the parcel has no valid geocode. Example: 38.906297
Longitude of the parcel centroid in decimal degrees (mirrors `coordinates.longitude`). Omitted when the parcel has no valid geocode. Example: -77.027766
GeoJSON Point at the parcel centroid, suitable for geospatial indexing and queries. Coordinates are `[longitude, latitude]` per the GeoJSON spec. Omitted when the parcel has no valid geocode. Example: `{ "type": "Point", "coordinates": [-77.027766, 38.906297] }`
GeoJSON geometry type — always "Point".
`[longitude, latitude]` of the parcel centroid. Example: \[-77.027766, 38.906297]
Geographic coordinates of the parcel centroid.
Latitude of the parcel centroid. Example: 38.906297
Longitude of the parcel centroid. Example: -77.027766
Parcel boundary as a GeoJSON MultiPolygon (single-polygon boundaries are wrapped to MultiPolygon). Omitted when no boundary was matched for the parcel — see `geometrySource`.
GeoJSON geometry type — always "MultiPolygon".
MultiPolygon coordinate array per the GeoJSON spec: an array of polygons, each an array of linear rings, each ring an array of `[longitude, latitude]` positions.
Provenance of the parcel boundary in `geometry`: "apn\_match" (boundary matched by parcel number), "point\_in\_parcel" (boundary matched by the parcel's geocoded point falling inside a polygon), or "none" (no boundary matched; `geometry` is omitted). Example: "apn\_match"
Tax jurisdiction identifiers, parcel IDs, and current ownership.
Municipality, township, or ward name within the county. Example: "WARD 2"
City name for tax jurisdiction purposes. Example: "WASHINGTON"
County name. Example: "DISTRICT OF COLUMBIA"
State abbreviation. Example: "DC"
Primary parcel identifier (tax map parcel ID) — same value as the top-level `parcelId`. Example: "0314- -0009"
Tax account or assessment account number.
Combined map and parcel identifier (e.g., "MAP-PARCEL" format).
Combined map, block, and lot identifier (e.g., "MAP-BLOCK-LOT" format).
A prior or alternate parcel identifier for the same physical property (e.g., a superseded assessor parcel number or an alternate county/tax-authority ID).
Numeric county code assigned by the state.
Numeric parcel sequence number within the tax district.
Tax district group number that this parcel belongs to.
Tax map sheet or cadastral map reference used by the assessor to index this parcel.
Special assessment code — an additional tax levy for specific public improvements (e.g., street reconstruction, sewer, sidewalks) benefiting this parcel.
URL of the county assessor's property detail page for this parcel.
Current owner of record with name and mailing address (from county assessor records).
Full name of the property owner. Example: "6 TREE LLC"
Second owner's full name when title is jointly held (e.g., spouse or co-owner).
Whether the owner of record occupies the property (owner-occupancy flag from the source feed).
Owner mailing address street. Example: "11654 PLAZA AMERICA DR"
Owner mailing address city. Example: "RESTON"
Owner mailing address state. Example: "VA"
Owner mailing address ZIP code. Example: "20190"
Owner mailing address ZIP+4 extension. Example: "4700"
Owner mailing address (street line only).
Owner full mailing address (street, city, state, ZIP).
Physical (situs) address of the parcel. The owner mailing address lives in `propertyIdentification.currentOwner`.
Formatted property address (street line only). Example: "1217 12TH ST NW"
Full, formatted property address (street line + city + state + ZIP).
Unformatted property address as it appears in the county source record. Example: "1217 12TH ST NW"
Street line: direction prefix + name + type + direction suffix. Example: "12TH ST NW"
Street number. Example: "1217"
Directional prefix (e.g., "N", "SW").
Street name without number, direction, or type. Example: "12TH"
Street type suffix. Example: "ST"
Directional suffix. Example: "NW"
Unit, apartment, or suite number.
City of the property's physical location. Example: "WASHINGTON"
State of the property's physical location. Example: "DC"
5-digit ZIP code. Example: "20005"
ZIP+4 extension (4 digits).
US Census tract identifier. Example: "005004"
US Census block identifier (finer-grained than tract). Example: "1000"
Full 5-digit FIPS code (state + county). Example: "11001"
2-digit FIPS state code. Example: "11"
3-digit FIPS county code. Example: "001"
Parsed address line 1 (street address without unit). Example: "1217 12TH ST NW"
Parsed address line 2 (unit designator, e.g., "APT 4B").
Address as delivered by the county source, prior to normalization. Example: "1217 12TH ST NW"
Formal parsed address rendering with words spelled out. Example: "1217 12TH STREET NORTHWEST"
Street address with the unit appended (base address + unit).
Computed full address string (address + unit, city, state, ZIP). Example: "1217 12TH ST NW, WASHINGTON, DC 20005"
USPS-normalized computed full address string. Example: "1217 12TH ST NW, WASHINGTON, DC 20005"
Unit number with designator words stripped (e.g., "APT 4B" → "4B").
USPS-normalized city name. Example: "WASHINGTON"
USPS-normalized county name (uppercase, no suffix). Example: "DISTRICT OF COLUMBIA"
USPS carrier route code for the situs address. Example: "C016"
## Classification, utilities & rooms
Property type, use codes, and administrative district assignments from county assessor records. The parcel's zoning designation lives in the top-level `zoningInfo` object.
Broad property class as a Realie `PC####` code; decode with the [Property Feature Field Key](/api-reference/v3/feature-key). Example: "PC0001" (RESIDENTIAL)
Property use code (4-digit scheme, unchanged code identities); decode with the [Property Feature Field Key](/api-reference/v3/feature-key). Example: "1110"
State-standardized land-use code, distinct from the county's local code and from `propertyUseCode`.
County-native land-use code as recorded by the local assessor. Example: "024"
Whether the property is classified as residential, derived from the property use code. Example: false
Assessor neighborhood code or name.
City used for classification and zoning purposes.
Numeric city code.
City section or ward identifier.
School district the parcel belongs to. Example: "District of Columbia Public Schools"
First special service district the parcel belongs to (e.g., fire, water, sewer).
Second special service district the parcel belongs to.
Development phase number within a subdivision.
Tract number within a subdivision.
Whether the property is a condominium, derived from the property use code. Example: false
Property-level counts (buildings, mobile homes, units).
Total number of buildings on the parcel. Example: 1
Total number of mobile homes on the parcel.
Total number of dwelling units across all buildings. Example: 2
Utility connections for the parcel, as Realie codes. Heating and cooling systems are documented in the top-level `heating` and `cooling` objects and per building under `buildingInformation.buildings`.
Water service (`WS####` — municipal, well, ...); decode with the [Property Feature Field Key](/api-reference/v3/feature-key). Example: "WS0001" (MUNICIPAL)
Sewer service (`SW####` — municipal, septic, ...); decode with the [Property Feature Field Key](/api-reference/v3/feature-key). Example: "SW0001" (MUNICIPAL)
Gas service (`GS####`); decode with the [Property Feature Field Key](/api-reference/v3/feature-key). Vocabulary published; not yet populated in the current data generation.
Electric service (`ES####`); decode with the [Property Feature Field Key](/api-reference/v3/feature-key). Vocabulary published; not yet populated in the current data generation.
Property-level room totals across all buildings. Per-building room counts are in `buildingInformation.buildings` (totalBedrooms, totalBathrooms, etc.).
Total number of rooms across all buildings on the property. Example: 8
Total bedrooms across all buildings. Example: 3
Total bathrooms across all buildings, as a decimal — half baths count as 0.5. Example: 2.0
Total full bathrooms (toilet + sink + tub/shower) across all buildings. Example: 2
Total half bathrooms (toilet + sink only) across all buildings. Example: 0
Total plumbing fixtures across all buildings.
Accessory structures and yard improvements recorded as simple line items in county assessor records (sheds, fences, decks, pools, detached carports). Structures with detailed characteristics (year built, rooms, construction type) appear in `buildingInformation.buildings` instead.
Building card or improvement number this item belongs to.
Item type (e.g., "Shed", "Fence", "Deck", "Pool", "Detached Carport").
Assessed value of the item.
Additional description or details about the item.
Unit of measure for area (e.g., "SF", "LF").
Area or length measurement in the specified units.
## Buildings
Coded characteristics of the parcel's primary building, promoted to the top level. Every coded member stores a Realie code — decode with the [Property Feature Field Key](/api-reference/v3/feature-key). The same member set appears per building under `buildingInformation.buildings[].characteristics`.
Specific building form (`BT####`). Example: "BT0003" (DUPLEX)
Property sub-type (`PS####`). Example: "PS0001" (CONDOMINIUM UNIT)
Construction class of the building shell (`BC####`).
Height class (`HB####`).
Level configuration (`BL####`).
Footprint shape (`BH####`).
Architectural style (`AS####`). Example: "AS0001" (RANCH)
Floor-plan layout (`FP####`).
Primary structural construction (`CT####`). Example: "CT0003" (MASONRY)
How the building was produced (`CM####`).
Exterior wall covering or material (`EW####`). Example: "EW0002" (BRICK)
Interior wall finish material (`IW####`). Example: "IW0001" (DRYWALL)
Roof covering material (`RM####`). Example: "RM0003" (METAL)
Roof geometry (`RS####`). Example: "RS0001" (GABLE)
Floor covering material (`FL####`). Example: "FL0002" (WOOD)
Foundation type (`FN####`). Vocabulary published; not yet populated in the current data generation.
Basement presence and type (`BS####`).
Attic presence and finish (`AT####`). Vocabulary published; not yet populated in the current data generation.
Physical condition on an integer 1–20 ordinal scale (1 worst, 20 best) — a number, not an opaque code. Scale anchors in the [Property Feature Field Key](/api-reference/v3/feature-key). Example: 10
Construction quality on an integer 1–20 ordinal scale (1 lowest) — a separate fact from `condition`; the two share only the scale form. Scale labels in the [Property Feature Field Key](/api-reference/v3/feature-key). Example: 11
Parking arrangement (`PK####`). Example: "PK0001" (ATTACHED GARAGE)
Driveway characteristics.
Driveway surface material (`DM####`). Example: "DM0001" (CONCRETE)
Driveway form (`DT####`). Example: "DT0001" (DRIVEWAY, TYPE UNSPECIFIED)
Pool characteristics.
Whether any pool or spa is present. Example: true
Pool or spa type (`PT####`); omitted when the source records a pool without a type. Example: "PT0001" (SPA OR HOT TUB)
Pool features (`PF####`); a pool can carry several.
Recorded amenities (`AM####`); a building can carry several. Example: \["AM0001"] (IRRIGATION SPRINKLER SYSTEM)
Additional named rooms (`OR####`). Example: \["OR0001"] (FAMILY ROOM OR DEN)
What kind of measurement the building's headline `buildingArea` represents (`BA####`). Example: "BA0001" (LIVING AREA)
Development type of the building's setting (`DV####`).
Construction/completion status (`DS####`).
Historic designation (`HT####`).
Age class (`AC####`).
Heating system of the primary building, described by five independent facets — counties record different aspects of the same system, so any subset may be present. All facets are Realie codes; decode with the [Property Feature Field Key](/api-reference/v3/feature-key). Per-building heating is under `buildingInformation.buildings[].heating`.
Heating equipment (`HE####`). Example: "HE0001" (HEAT PUMP)
How heat is delivered (`HD####`). Example: "HD0001" (FORCED AIR)
Fuel or energy source (`HS####`). Example: "HS0001" (NATURAL GAS)
System configuration (`HC####`). Example: "HC0001" (CENTRAL)
Whether (and how completely) the building is heated, used when the source proves presence without naming the system (`HX####`).
Cooling system of the primary building. Per-building cooling is under `buildingInformation.buildings[].cooling`.
Cooling equipment (`CL####`); decode with the [Property Feature Field Key](/api-reference/v3/feature-key). Example: "CL0001" (CENTRAL)
Container for all improved structures on the parcel. Covers main dwellings, guest houses, detached garages, barns — any building carrying detailed assessor characteristics (year built, construction, rooms, square footage). Simple accessory structures and yard improvements with only a type/description/area/value are listed under `outbuildingsYardItems` instead.
List of all improved structures on the parcel, each with detailed appraisal characteristics from county assessor records.
```json example theme={null}
"buildings": [
{
"stories": 2.0,
"livingArea": 1628.0,
"buildingArea": 2348.0,
"buildingAreas": [
{ "area": 2348.0, "areaUnits": "SF", "areaType": "BA0003", "squareFeet": 2348.0 },
{ "area": 720.0, "areaUnits": "SF", "areaType": "BA0015", "squareFeet": 720.0 }
],
"actualYearBuilt": 1900,
"effectiveYearBuilt": 1967,
"totalBedrooms": 3,
"totalBathrooms": 2.0,
"fullBathrooms": 2,
"halfBathrooms": 0,
"characteristics": {
"exteriorWall": "EW0002",
"roofMaterial": "RM0003",
"roofStyle": "RS0001",
"flooring": "FL0002",
"basement": "BS0001",
"construction": "CT0003",
"architecturalStyle": "AS0001",
"quality": 11,
"condition": 10,
"buildingAreaType": "BA0003",
"pool": { "exists": false }
},
"heating": {
"distribution": "HD0001",
"energySource": "HS0001"
},
"cooling": { "equipment": "CL0001" },
"pool": false,
"fireplaceCount": 2,
"garage": false,
"garageCount": 0
}
]
```
Building sequence number on the parcel (1 = primary building).
Assessed or appraised value of this building, also known as improvement value.
Number of stories in this building; half-stories are decimals (e.g., 1.5). Example: 2
Total heated/finished living area of this building in square feet. Example: 1628
Total building area in square feet; `characteristics.buildingAreaType` says what kind of measurement it represents. Example: 2348
Breakdown of this building's areas by section (e.g., ground floor, gross, garage, basement).
Numeric area value in the units specified by `areaUnits`. Example: 2348
Unit of measure for `area` (e.g., "SF" for square feet, "LF" for linear feet). Example: "SF"
The kind of measured area this entry represents, as a Realie `BA####` code (living area, gross area, garage, basement, ...). Decode with the [Property Feature Field Key](/api-reference/v3/feature-key). Example: "BA0003" (GROSS AREA)
The same measurement converted to square feet. Example: 2348
Original year the building was constructed. Example: 1900
Effective year built after renovations — reflects condition, not original construction. Example: 1967
Number of bedrooms in this building. Example: 3
Total bathroom count in this building; half baths count as 0.5 (e.g., 2.5). Example: 2
Number of full bathrooms (toilet + sink + tub/shower). Example: 2
Number of half bathrooms (toilet + sink only). Example: 0
Total plumbing fixture count for this building.
This building's coded characteristics — identical member set and vocabularies as the top-level `building` object documented above (buildingType, architecturalStyle, construction, exteriorWall, roofMaterial, flooring, basement, condition, quality, parking, driveway, pool, amenities, otherRooms, buildingAreaType, and the rest). All coded members store Realie codes; decode with the [Property Feature Field Key](/api-reference/v3/feature-key).
This building's heating system — identical facet set as the top-level `heating` object documented above (equipment, distribution, energySource, configuration, coverage).
This building's cooling system — identical member set as the top-level `cooling` object documented above (equipment).
Roof framing type (e.g., "Truss", "Rafter"). Not populated in the current data generation.
Floor structural system (e.g., "Joist", "Slab on Grade"). Not populated in the current data generation.
Cabinet and millwork quality grade. Not populated in the current data generation.
Paint and decor quality grade. Not populated in the current data generation.
Bathroom tile quality or type. Not populated in the current data generation.
Whether the building has a pool; mirrors `characteristics.pool.exists`. Example: false
Whether the building has a fireplace.
Number of fireplaces. Example: 2
Whether the building has a garage. Example: false
Number of garage bays or spaces. Example: 0
## Land, valuation, tax & legal
Aggregate land measurements, lot dimensions, and land classification for the parcel.
Acreage as stated on the recorded deed.
Total parcel acreage from county assessor records. Example: 0.0425
Acreage calculated from GIS or survey data rather than stated on the deed.
Total land area in the units specified by `landAreaUnits`. Example: 1853
Unit of measure for `totalLandArea` (e.g., "AC" for acres, "SF" for square feet).
Lot depth in feet.
Lot frontage (street-facing width) in feet.
Site topography (`TP####` — level, rolling, hilly, ...); decode with the [Property Feature Field Key](/api-reference/v3/feature-key). Example: "TP0001" (LEVEL GRADE)
Road access to the parcel (`RA####`); decode with the [Property Feature Field Key](/api-reference/v3/feature-key). Vocabulary published; not yet populated in the current data generation.
Waterfront type (`WF####`); decode with the [Property Feature Field Key](/api-reference/v3/feature-key). Vocabulary published; not yet populated in the current data generation.
View quality (`VQ####`); decode with the [Property Feature Field Key](/api-reference/v3/feature-key). Vocabulary published; not yet populated in the current data generation.
Breakdown of the parcel into land segments by use code or soil class.
Land use or soil classification code for this parcel segment. Not populated in the current data generation.
Soil productivity class or rating. Not populated in the current data generation.
Numeric area measurement for this land segment in the units specified by `areaUnits`.
Unit of measure for `area` (e.g., "AC", "SF", "FF").
Area of this land segment in acres.
Area of this land segment in square feet.
Total assessed value of this land segment.
Assessor valuation figures and tax exemptions for the parcel.
Total market value of the property (land plus buildings) from county assessor records. Example: 1184520
Total assessed value used for tax calculation. Example: 1184520
Assessed or appraised value of all buildings/improvements (also known as total improvement value). Example: 479530
Assessed or appraised value of the land only. Example: 704990
Total just/fair market value, used in Florida and similar jurisdictions.
Taxable value after exemptions are applied — the basis tax is actually levied against. Differs from `totalAssessedValue` when exemptions exist.
Tax year the assessment applies to. Example: 2025
Year the appraisal was performed.
Tax exemptions applied to the property.
Exemption type as a readable value — no decode table needed. Values include "Homestead", "Senior", "Veteran", "School/College", "Disabled", "Widow", "Religious". Example: "Homestead"
Dollar amount of the exemption.
Additional description or details about the exemption.
Total dollar value of all exemptions combined.
Tax amounts, districts, and historical tax records for the parcel.
Total tax amount due or paid for the current tax year. Example: 59226
Tax year the record applies to. Example: 2025
Tax district name.
The assessor's tax-district code for the parcel, where the source provides one — the district identifier the county assessor levies against, carried verbatim. Jurisdiction-issued: meaningful within its county, not part of the national code system, and format varies by county (numeric codes, structured codes, or district names). Example: "01"
Tax classification of the parcel (`TC####`); decode with the [Property Feature Field Key](/api-reference/v3/feature-key). Vocabulary published; not yet populated in the current data generation.
Explicit tax status when the source feed semantically proves it: "current", "exempt", "delinquent", or "not\_available"; omitted when status is unknown. Only "delinquent" is emitted in the current data generation. Example: "delinquent"
Tax-levying jurisdiction; may differ from the zoning jurisdiction.
URL to the county tax record or tax bill.
Historical tax records by year.
Tax year this record applies to.
Total tax amount due or paid for that year.
Description of what the tax is for (e.g., "Property Tax", "School Tax", "Municipal Tax").
Payment status (e.g., "Paid", "Unpaid", "Delinquent", "Partial").
Date the tax bill was paid.
Date the tax bill is or was due.
Recorded legal description, subdivision/plat identifiers, and Public Land Survey System references.
Full legal description of the property as recorded. Example: "SQUARE 0314 LOT 0009 NBHD: OLD CITY 2"
Reference to the recorded legal document (e.g., deed book/page).
Name of the subdivision or plat. Example: "OLD CITY 2"
Public Land Survey System (PLSS) section number.
Public Land Survey System (PLSS) township designation.
Public Land Survey System (PLSS) range designation.
Block number within the subdivision plat. Example: "314"
Lot number within the block. Example: "9"
Lot composition of the legal parcel (`LT####` — more than one lot, partial lot, ...); decode with the [Property Feature Field Key](/api-reference/v3/feature-key). Example: "LT0001" (MORE THAN ONE LOT)
Land lot number, used in metes-and-bounds states such as Georgia.
URL to the recorded deed document.
## Sales history
Chronological list of recorded sale and transfer events for the parcel, from county recorder records — each entry carries the price, dates, deed references, and parties. In the v2-legacy flat shape these events are exposed as `transfers[]`, where `saleCode` corresponds to `qualification` here.
Date the sale was executed (YYYY-MM-DD format). Example: "2019-12-17"
Date the deed was recorded with the county (YYYY-MM-DD format). Example: "2020-01-16"
Recorded sale price in dollars. May be 0 for nominal-consideration or non-disclosure transfers — check `armsLength` and `qualification` before treating it as a market price. Example: 1400000
Combined deed book and page reference for the recorded instrument (e.g., "1234/567").
Deed book number of the recorded instrument.
Deed page number of the recorded instrument.
Recorded instrument (deed) type on the event (`TT####`). Decode with the [Property Feature Field Key](/api-reference/v3/feature-key). Example: "TT0001" (WARRANTY DEED)
Recorder's document or instrument number for the sale. Mortgages that financed a sale reference this value via `mortgages[].relatedSaleDocumentNumber`. Example: "2020.6827"
Sale-qualification code (`TQ####`) saying why the sale is — or is not — considered a market (arm's-length) transaction. Omitted when the source recorded no reviewed qualification signal for the sale. Decode with the [Property Feature Field Key](/api-reference/v3/feature-key). In the v2-legacy flat shape this is exposed as `transfers[].saleCode`. Example: "TQ0002" (VALID ARM'S-LENGTH SALE)
Whether the sale is considered an arm's-length market transaction — the boolean verdict carried alongside `qualification`. Omitted when the source supplied no qualification verdict for the sale, including on nearly all events recorded after March 2026, where the determination lags the recording; read `qualification` for those. Example: true
Whether the property was vacant or improved at the time of sale. Not populated in the current data generation.
Whether the sale was distressed (foreclosure, short sale, etc.), as flagged in recorder records.
Whether the property was REO (bank-owned, post-foreclosure) at the time of sale, as flagged in recorder records.
Documentary transfer / excise tax paid on the sale, in dollars. Example: 0
Title company that handled the recorded transaction. Example: "ALLIED TITLE & ESCROW LLC"
Seller name in this transaction. Example: "MARR NELSON P"
Second seller/grantor name when the property was sold by co-sellers. Example: "MARR LISETTE M"
Buyer name in this transaction. Example: "6 TREE LLC"
Second buyer/grantee name when the property was bought by co-buyers.
What kind of entity the buyer is (`BE####` — individual, company, trust, ...). Decode with the [Property Feature Field Key](/api-reference/v3/feature-key). Example: "BE0001" (INDIVIDUAL(S))
Relationship between co-buyers (`BR####`). Decode with the [Property Feature Field Key](/api-reference/v3/feature-key). Example: "BR0001" (HUSBAND AND WIFE)
Legal role the buyer takes in the transfer (`RO####`). Decode with the [Property Feature Field Key](/api-reference/v3/feature-key). Example: "RO0001" (BENEFICIARY/CREDITOR)
How the buyer holds title (`BV####` — joint tenants, tenants in common, community property, ...). Decode with the [Property Feature Field Key](/api-reference/v3/feature-key). Example: "BV0001" (JOINT TENANTS)
How the recorded sale-price figure was obtained (`PD####` — stated on the document, computed from transfer tax, ...). Decode with the [Property Feature Field Key](/api-reference/v3/feature-key). Example: "PD0001" (STATED ON DOCUMENT)
## Mortgages, liens & foreclosures
Mortgages and deeds of trust recorded against the property — purchase-money loans and refinances, sourced from county recorder records and sorted newest-first. Each entry carries the lender, loan terms, lien position, a link to the sale it financed (if any), and the loan's own post-origination custody chain (assignments and releases). A key is absent when the source record has no value.
```json example theme={null}
"mortgages": [
{
"amount": 308000,
"lender": "AURORA FINANCIAL LLC",
"interestRate": 4.0,
"interestRateType": "IR0001",
"term": 360,
"termUnit": "months",
"loanType": "LN0001",
"lienPosition": "first",
"recordingDate": "2017-03-21",
"documentNumber": "2017.30971",
"dueDate": "2047-04-01",
"loanTransactionType": "LX0001",
"adjustableRateRider": true,
"firstRateChangeYear": 24,
"riders": ["RD0003"]
}
]
```
Loan amount in dollars. Example: 308000
Lender / beneficiary name as recorded. Example: "AURORA FINANCIAL LLC"
Interest rate, in percent. Example: 4.0
Interest-rate structure (`IR####` — fixed, variable, ...). Decode with the [Property Feature Field Key](/api-reference/v3/feature-key). Example: "IR0001" (VARIABLE RATE)
Loan term length, in the unit given by termUnit. Example: 360
Unit of the loan term. Currently always "months". Example: "months"
Loan product or program (`LN####`). Decode with the [Property Feature Field Key](/api-reference/v3/feature-key). Example: "LN0001" (CONVENTIONAL LOAN)
Amortization structure (`LA####` — balloon, ...). Decode with the [Property Feature Field Key](/api-reference/v3/feature-key). Example: "LA0001" (BALLOON)
Lien priority at origination: "first" (senior) or "second" (junior/piggyback). Carried on the source record — not derivable from date, since first and second mortgages are typically recorded at the same closing. Example: "first"
Date the mortgage was recorded (YYYY-MM-DD format). Example: "2017-03-21"
Recorder's document number for the mortgage. Example: "2017.30971"
Loan maturity / due date (YYYY-MM-DD format). Example: "2047-04-01"
Source loan identifier used to link this loan to its assignment/release records.
Document number of the sale this loan financed, if any — links to a salesHistory entry's saleDocumentNumber. Absent for a standalone refinance. Example: "2020.6827"
What the loan financed (`LX####` — purchase, refinance, construction, ...). Decode with the [Property Feature Field Key](/api-reference/v3/feature-key). Example: "LX0001" (REFINANCE / SECOND TRUST DEED)
Whether this loan is a refinance. Example: true
Whether this loan is a home equity line of credit. Example: true
Whether this loan is a home-equity loan. Example: true
Whether this loan is a construction loan.
Whether interestRate is estimated rather than recorded. Example: true
Whether the seller carried back financing.
Whether the lender is a private party rather than an institution.
Whether an adjustable-rate rider is present on the recorded mortgage. Example: true
Index the adjustable rate is tied to (`RI####`). Decode with the [Property Feature Field Key](/api-reference/v3/feature-key). Example: "RI0001" (LIBOR 1-YEAR)
Lifetime maximum (cap) interest rate, in percent.
Lifetime minimum (floor) interest rate, in percent.
Interest-only period length in months, if any.
How often the adjustable rate may change, as an interval in years — a numeric quantity, not a code (e.g. `1.0` = annually, `0.083` ≈ monthly). Example: 1.0
Year of the first scheduled rate change, as recorded (may appear as a two-digit year). Example: 24
Riders recorded on the mortgage instrument (`RD####` — planned unit development, condominium, second home, balloon, ...); an instrument can carry several. Decode each entry with the [Property Feature Field Key](/api-reference/v3/feature-key). Example: \["RD0003"] (1-4 FAMILY RIDER)
This loan's post-origination custody chain — assignments (lender-to-lender transfers) and releases/reconveyances — in recording order, joined to the loan from recorder assignment and release records.
"assignment" (the loan is transferred to a new holder) or "release" (the loan is satisfied/reconveyed). Example: "assignment"
Date this assignment/release was recorded (YYYY-MM-DD format). Example: "2025-01-21"
Lender assigning or releasing the loan (the current holder). Example: "CENTER STREET LENDING VIII SPE LLC"
Lender the loan is assigned to. Assignments only — absent for releases. Example: "CENTER STREET LENDING RIO IX LLC"
Original amount of the mortgage being assigned/released, in dollars. Example: 80000
Recording date of the original mortgage being assigned/released (YYYY-MM-DD format). Example: "2024-11-07"
Document number of the original mortgage being assigned/released. Example: "105276"
Recorder's document number for this assignment/release record. Example: "6692"
Borrower on the underlying loan. Example: "6 TREE LLC"
Involuntary liens and judgments recorded against the property — tax liens, judgments, mechanic's liens, UCC filings — sourced from county recorder records. A key is absent when the source record has no value.
Type of the recorded lien or judgment (`LI####`). Decode with the [Property Feature Field Key](/api-reference/v3/feature-key). Example: "LI0001" (FINANCING STATEMENT)
Date the lien was recorded (YYYY-MM-DD format).
Recorder's document number for the lien.
Lien / judgment amount in dollars.
Lien holder / creditor — the party the lien is in favor of.
Debtor — the party the lien is against.
Court or case number associated with the lien, if any.
Document number of a related/referenced instrument (e.g., the underlying loan).
Pre-foreclosure and foreclosure events recorded against the property — notices of default, notices of sale, lis pendens, and auctions — sourced from county recorder records. A key is absent when the source record has no value.
Type of the recorded foreclosure event (`FR####` — lis pendens, notice of default, notice of sale, ...). Decode with the [Property Feature Field Key](/api-reference/v3/feature-key). May be absent on records restored from the pre-v3 pipeline whose event class has no code in the published vocabulary. Example: "FR0002" (NOTICE OF DEFAULT)
Date this foreclosure record was recorded (YYYY-MM-DD format).
Court filing date (YYYY-MM-DD format), when distinct from the recording date. Populated on records restored from the pre-v3 pipeline, which recorded both dates.
Recorder's document number for this record.
Court or trustee case number.
Date of default (YYYY-MM-DD format).
Unpaid loan balance at filing, in dollars.
Amount past due at filing, in dollars.
Scheduled foreclosure-auction / trustee-sale date (YYYY-MM-DD format).
Scheduled auction time, as free text as recorded.
Scheduled auction location.
Minimum auction bid amount, in dollars.
Lender / beneficiary on the defaulted loan.
Trustee handling the foreclosure.
Borrower in default.
Original amount of the defaulted loan, in dollars.
## Histories, valuation model & extensions
Historical appraised values by year from county assessor records — one entry per appraisal year, with land, building, and total market components.
Year of the appraisal. Example: 2024
Appraised value of buildings/improvements for this year (also known as improvement value).
Appraised value of land for this year.
Total appraised market value for this year.
Historical assessed values by year from county assessor records — one entry per assessment year, with land, building, total, and market components.
Year of the assessment. Example: 2025
Assessed value of buildings/improvements for this year (also known as improvement value). Example: 479530
Assessed value of land for this year. Example: 704990
Total assessed value for this year. Example: 1184520
Market value recorded alongside the assessment for this year, where the county exposes both. Example: 1184520
Year the market value applies to, when distinct from `assessmentYear`. Example: 2025
Building and construction permits associated with the property, sourced from the issuing jurisdiction's permit records.
Permit number or ID assigned by the issuing authority.
Authority that issued the permit (e.g. "City of Tampa", "Hillsborough County") — useful when permits cross municipal/county boundaries.
Short description of the permitted work.
Date the permit was issued (YYYY-MM-DD).
Estimated value of the permitted work as stated on the application.
Permit type (e.g., "Building", "Electrical", "Plumbing", "Mechanical").
Current status (e.g., "Issued", "Final", "Expired", "Void").
Date the permit application was submitted (YYYY-MM-DD).
Date the permit received final inspection/approval (YYYY-MM-DD).
Date the permit expires (YYYY-MM-DD).
Detailed description of the permitted work.
Licensed contractor name.
Contractor license number.
Contractor business address.
Contractor phone number.
Official valuation of the permitted work (may differ from the estimated value on the application).
Square footage affected by the permitted work.
Number of stories affected by the permitted work.
Number of units affected by the permitted work.
Most recent inspection status (e.g., "Passed", "Failed", "Pending").
Total number of inspections performed.
Date of the most recent inspection (YYYY-MM-DD).
Total permit fees charged in dollars.
Additional notes or comments on the permit.
URL to the permit record on the issuing jurisdiction's site.
Electricity utility and rate information for the property's service area.
Name of the electric utility serving this property.
EIA (U.S. Energy Information Administration) utility identifier.
Rate schedule name or code.
Default/Tier 1 residential rate in \$/kWh.
Monthly fixed service charge in dollars.
Date the rate became effective (YYYY-MM-DD).
Estimated monthly consumption in kWh, derived from building square footage and type.
Estimated monthly electricity cost (rate × estimated kWh + fixed charge).
Rate data source: "urdb" (Utility Rate Database) or "scraped".
URL where the rate data was sourced from.
The parcel's zoning designation with provenance — the record's one zoning surface. `matchMethod` says which of the two provenance tiers produced it.
Zoning district code as issued by the zoning jurisdiction (e.g., "R-1", "B-2", "AG-1"). Jurisdiction-issued — interpret within `zoningJurisdiction`, not as a national vocabulary.
Human-readable zoning description (e.g., "Single Family Residential").
Regulatory body that administers the zoning (e.g., "HAMMOND", "LAKE COUNTY").
Identifier of the dataset the zoning designation was sourced from (e.g., "IN\_LAKE\_HAMMOND").
How the designation was matched to the parcel: "assessor\_recorded" (baseline — the designation as recorded on the county assessor's own record for the parcel) or "gis\_point\_in\_polygon" (curated — the parcel's point located inside the zoning jurisdiction's GIS zoning layer). Example: "gis\_point\_in\_polygon"
Availability flags and links for supplementary property resources — building sketches, property card PDFs, photos, and GIS maps.
Whether a building sketch/floor plan is available.
URL to the building sketch or floor plan document.
Whether the assessor property card PDF is available for download.
URL or reference to parcel photo(s).
Whether a GIS/parcel map is available.
URL to the GIS or parcel map viewer.
URLs to external property resources hosted by the county or its mapping providers.
URL to the county's comparable sales search tool.
URL to the Pictometry/aerial photo viewer.
URL to the metro or county map viewer.
Catch-all for additional source data that does not fit the structured sections, serialized as a JSON string. Structure varies by county.
Realie's own automated valuation (AVM): two independent estimators that cross-check each other — a machine-learning estimate with universal coverage (`ml`) and a comparable-sales estimate where enough nearby comps exist (`comp`).
Realie's machine-learning AVM estimate. Produced for essentially all valued parcels.
Calibrated ML point estimate of market value, in dollars.
Lower bound of the estimate band (30th percentile), in dollars.
Upper bound of the estimate band (70th percentile), in dollars.
Model ensemble disagreement, in dollars — larger values indicate a less certain estimate.
Confidence tier from 0 to 100.
Confidence label: "very\_high", "high", "medium", "low", or "very\_low".
Model version identifier for the estimate. Example: "v3-noassessor-2026-06-13"
Realie's comparable-sales estimate — K-nearest recent comparable sales, no ML. Absent where comparable sales are too sparse.
Comparable-sales point estimate (median comparable \$/sqft × living area), in dollars.
Lower bound of the comp estimate band (25th percentile), in dollars.
Upper bound of the comp estimate band (75th percentile), in dollars.
Median price per square foot across the comparable sales used.
Number of comparable sales used in the estimate.
Distance in miles to the farthest comparable used — a comp-density/confidence signal.
Trailing lookback window for comparable sales, in months.
Comp-model version identifier for the estimate. Example: "compval-knn10-2026-06-13"
Date the valuation was scored (YYYY-MM-DD) — the "estimated as of" date.
Modeled debt/equity analytics carried over from the legacy v2 pipeline. These are modeled estimates (open-lien rollups, current-LTV/equity models), not recorded facts — recorded mortgages and liens live in their own history arrays and are never derived from this object. Present only on parcels uniquely matched to a legacy v2 record. Excluded from API responses; available in bulk data only.
Modeled count of open liens against the parcel. Example: 2
Modeled total open lien balance in dollars. Example: 4377540
Count of financing events in the legacy analytics model. Example: 8
Estimated current combined loan-to-value ratio, as a percentage. Example: 311.5685
Band index for the modeled current LTV — an ordered integer bucket, not a percentage and not an uncertainty spread. Band boundaries are not published; treat as ordered buckets. Example: 14
Estimated current owner equity in dollars (negative when modeled debt exceeds modeled value). Example: -2972539
Band index for the modeled current equity — an ordered integer bucket over dollar ranges, not a dollar amount. Band boundaries are not published; treat as ordered buckets. Example: 65
Loan-to-value ratio at purchase, as a percentage. Example: 75
Most recent lender name in the legacy debt model. Example: "CENTER STREET LENDING CORPORATION"
Ownership-tenure analytics carried over from the legacy v2 pipeline. Keyed to the v2-era owner of record and may lag the current owner in `propertyIdentification.currentOwner`. Present only on parcels uniquely matched to a legacy v2 record. Excluded from API responses; available in bulk data only.
Date the (v2-era) current ownership began (YYYYMMDD). Example: "20191217"
Owner tenure at the property in months. Example: 72
Owner-tenure band — an integer band index 1–8; higher bands mean longer tenure. Band boundaries are not published; prefer `lengthOfResidenceMonths` when present. Example: 4
Number of parcels held by the same owner, per the legacy owner match. Example: 12
Residential parcels held by the same owner. Example: 10
Commercial parcels held by the same owner. Example: 2