Property Data Schema (v3)

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, 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). Accounts that haven’t switched receive the same data in the v2-compatible flat layout documented in the legacy tab; the migration guide 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).

Identity & location

string

Primary parcel identifier (Assessor’s Parcel Number / tax map parcel ID) as recorded by the county assessor. Example: “0314- -0009”

string

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”

string

Two-letter USPS state abbreviation for the parcel. Example: “DC”

string

Street number and street name of the property, promoted from propertyLocation.address. Example: “1217 12TH ST NW”

string

Property use code, promoted from propertyClassification.propertyUseCode. Coded value — decode with the Property Feature Field Key. Example: “1110”

string

5-digit ZIP code of the property, promoted from propertyLocation.zipCode. Example: “20005”

string

5-digit FIPS code (state + county) of the parcel’s county, promoted from propertyLocation.fipsCode. Example: “11001”

number

Latitude of the parcel centroid in decimal degrees (mirrors coordinates.latitude). Omitted when the parcel has no valid geocode. Example: 38.906297

number

Longitude of the parcel centroid in decimal degrees (mirrors coordinates.longitude). Omitted when the parcel has no valid geocode. Example: -77.027766

object

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] }

Show location properties

string

GeoJSON geometry type — always “Point”.

array

[longitude, latitude] of the parcel centroid. Example: [-77.027766, 38.906297]

object

Geographic coordinates of the parcel centroid.

Show coordinates properties

number

Latitude of the parcel centroid. Example: 38.906297

number

Longitude of the parcel centroid. Example: -77.027766

object

Parcel boundary as a GeoJSON MultiPolygon (single-polygon boundaries are wrapped to MultiPolygon). Omitted when no boundary was matched for the parcel — see geometrySource.

Show geometry properties

string

GeoJSON geometry type — always “MultiPolygon”.

array

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.

string

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”

object

Tax jurisdiction identifiers, parcel IDs, and current ownership.

Show propertyIdentification properties

string

Municipality, township, or ward name within the county. Example: “WARD 2”

string

City name for tax jurisdiction purposes. Example: “WASHINGTON”

string

County name. Example: “DISTRICT OF COLUMBIA”

string

State abbreviation. Example: “DC”

string

Primary parcel identifier (tax map parcel ID) — same value as the top-level parcelId. Example: “0314- -0009”

string

Tax account or assessment account number.

string

Combined map and parcel identifier (e.g., “MAP-PARCEL” format).

string

Combined map, block, and lot identifier (e.g., “MAP-BLOCK-LOT” format).

string

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).

string

Numeric county code assigned by the state.

string

Numeric parcel sequence number within the tax district.

string

Tax district group number that this parcel belongs to.

string

Tax map sheet or cadastral map reference used by the assessor to index this parcel.

string

Special assessment code — an additional tax levy for specific public improvements (e.g., street reconstruction, sewer, sidewalks) benefiting this parcel.

string

URL of the county assessor’s property detail page for this parcel.

object

Current owner of record with name and mailing address (from county assessor records).

Show currentOwner properties

string

Full name of the property owner. Example: “6 TREE LLC”

string

Second owner’s full name when title is jointly held (e.g., spouse or co-owner).

boolean

Whether the owner of record occupies the property (owner-occupancy flag from the source feed).

string

Owner mailing address street. Example: “11654 PLAZA AMERICA DR”

string

Owner mailing address city. Example: “RESTON”

string

Owner mailing address state. Example: “VA”

string

Owner mailing address ZIP code. Example: “20190”

string

Owner mailing address ZIP+4 extension. Example: “4700”

string

Owner mailing address (street line only).

string

Owner full mailing address (street, city, state, ZIP).

object

Physical (situs) address of the parcel. The owner mailing address lives in propertyIdentification.currentOwner.

Show propertyLocation properties

string

Formatted property address (street line only). Example: “1217 12TH ST NW”

string

Full, formatted property address (street line + city + state + ZIP).

string

Unformatted property address as it appears in the county source record. Example: “1217 12TH ST NW”

string

Street line: direction prefix + name + type + direction suffix. Example: “12TH ST NW”

string

Street number. Example: “1217”

string

Directional prefix (e.g., “N”, “SW”).

string

Street name without number, direction, or type. Example: “12TH”

string

Street type suffix. Example: “ST”

string

Directional suffix. Example: “NW”

string

Unit, apartment, or suite number.

string

City of the property’s physical location. Example: “WASHINGTON”

string

State of the property’s physical location. Example: “DC”

string

5-digit ZIP code. Example: “20005”

string

ZIP+4 extension (4 digits).

string

US Census tract identifier. Example: “005004”

string

US Census block identifier (finer-grained than tract). Example: “1000”

string

Full 5-digit FIPS code (state + county). Example: “11001”

string

2-digit FIPS state code. Example: “11”

string

3-digit FIPS county code. Example: “001”

string

Parsed address line 1 (street address without unit). Example: “1217 12TH ST NW”

string

Parsed address line 2 (unit designator, e.g., “APT 4B”).

string

Address as delivered by the county source, prior to normalization. Example: “1217 12TH ST NW”

string

Formal parsed address rendering with words spelled out. Example: “1217 12TH STREET NORTHWEST”

string

Street address with the unit appended (base address + unit).

string

Computed full address string (address + unit, city, state, ZIP). Example: “1217 12TH ST NW, WASHINGTON, DC 20005”

string

USPS-normalized computed full address string. Example: “1217 12TH ST NW, WASHINGTON, DC 20005”

string

Unit number with designator words stripped (e.g., “APT 4B” → “4B”).

string

USPS-normalized city name. Example: “WASHINGTON”

string

USPS-normalized county name (uppercase, no suffix). Example: “DISTRICT OF COLUMBIA”

string

USPS carrier route code for the situs address. Example: “C016”

Classification, utilities & rooms

object

Property type, use codes, and administrative district assignments from county assessor records. The parcel’s zoning designation lives in the top-level zoningInfo object.

Show propertyClassification properties

string

Broad property class as a Realie PC#### code; decode with the Property Feature Field Key. Example: “PC0001” (RESIDENTIAL)

string

Property use code (4-digit scheme, unchanged code identities); decode with the Property Feature Field Key. Example: “1110”

string

State-standardized land-use code, distinct from the county’s local code and from propertyUseCode.

string

County-native land-use code as recorded by the local assessor. Example: “024”

boolean

Whether the property is classified as residential, derived from the property use code. Example: false

string

Assessor neighborhood code or name.

string

City used for classification and zoning purposes.

string

Numeric city code.

string

City section or ward identifier.

string

School district the parcel belongs to. Example: “District of Columbia Public Schools”

string

First special service district the parcel belongs to (e.g., fire, water, sewer).

string

Second special service district the parcel belongs to.

string

Development phase number within a subdivision.

string

Tract number within a subdivision.

boolean

Whether the property is a condominium, derived from the property use code. Example: false

object

Property-level counts (buildings, mobile homes, units).

Show generalInformation properties

number

Total number of buildings on the parcel. Example: 1

number

Total number of mobile homes on the parcel.

number

Total number of dwelling units across all buildings. Example: 2

object

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.

Show utilities properties

string

Water service (WS#### — municipal, well, …); decode with the Property Feature Field Key. Example: “WS0001” (MUNICIPAL)

string

Sewer service (SW#### — municipal, septic, …); decode with the Property Feature Field Key. Example: “SW0001” (MUNICIPAL)

string

Gas service (GS####); decode with the Property Feature Field Key. Vocabulary published; not yet populated in the current data generation.

string

Electric service (ES####); decode with the Property Feature Field Key. Vocabulary published; not yet populated in the current data generation.

object

Property-level room totals across all buildings. Per-building room counts are in buildingInformation.buildings (totalBedrooms, totalBathrooms, etc.).

Show roomInformation properties

number

Total number of rooms across all buildings on the property. Example: 8

number

Total bedrooms across all buildings. Example: 3

number

Total bathrooms across all buildings, as a decimal — half baths count as 0.5. Example: 2.0

number

Total full bathrooms (toilet + sink + tub/shower) across all buildings. Example: 2

number

Total half bathrooms (toilet + sink only) across all buildings. Example: 0

number

Total plumbing fixtures across all buildings.

array

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.

Show outbuilding / yard item entry properties

number

Building card or improvement number this item belongs to.

string

Item type (e.g., “Shed”, “Fence”, “Deck”, “Pool”, “Detached Carport”).

number

Assessed value of the item.

string

Additional description or details about the item.

string

Unit of measure for area (e.g., “SF”, “LF”).

number

Area or length measurement in the specified units.

Buildings

object

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. The same member set appears per building under buildingInformation.buildings[].characteristics.

Show building properties

string

Specific building form (BT####). Example: “BT0003” (DUPLEX)

string

Property sub-type (PS####). Example: “PS0001” (CONDOMINIUM UNIT)

string

Construction class of the building shell (BC####).

string

Height class (HB####).

string

Level configuration (BL####).

string

Footprint shape (BH####).

string

Architectural style (AS####). Example: “AS0001” (RANCH)

string

Floor-plan layout (FP####).

string

Primary structural construction (CT####). Example: “CT0003” (MASONRY)

string

How the building was produced (CM####).

string

Exterior wall covering or material (EW####). Example: “EW0002” (BRICK)

string

Interior wall finish material (IW####). Example: “IW0001” (DRYWALL)

string

Roof covering material (RM####). Example: “RM0003” (METAL)

string

Roof geometry (RS####). Example: “RS0001” (GABLE)

string

Floor covering material (FL####). Example: “FL0002” (WOOD)

string

Foundation type (FN####). Vocabulary published; not yet populated in the current data generation.

string

Basement presence and type (BS####).

string

Attic presence and finish (AT####). Vocabulary published; not yet populated in the current data generation.

integer

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. Example: 10

integer

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. Example: 11

string

Parking arrangement (PK####). Example: “PK0001” (ATTACHED GARAGE)

object

Driveway characteristics.

Show driveway properties

string

Driveway surface material (DM####). Example: “DM0001” (CONCRETE)

string

Driveway form (DT####). Example: “DT0001” (DRIVEWAY, TYPE UNSPECIFIED)

object

Pool characteristics.

Show pool properties

boolean

Whether any pool or spa is present. Example: true

string

Pool or spa type (PT####); omitted when the source records a pool without a type. Example: “PT0001” (SPA OR HOT TUB)

array of strings

Pool features (PF####); a pool can carry several.

array of strings

Recorded amenities (AM####); a building can carry several. Example: [“AM0001”] (IRRIGATION SPRINKLER SYSTEM)

array of strings

Additional named rooms (OR####). Example: [“OR0001”] (FAMILY ROOM OR DEN)

string

What kind of measurement the building’s headline buildingArea represents (BA####). Example: “BA0001” (LIVING AREA)

string

Development type of the building’s setting (DV####).

string

Construction/completion status (DS####).

string

Historic designation (HT####).

string

Age class (AC####).

object

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. Per-building heating is under buildingInformation.buildings[].heating.

Show heating properties

string

Heating equipment (HE####). Example: “HE0001” (HEAT PUMP)

string

How heat is delivered (HD####). Example: “HD0001” (FORCED AIR)

string

Fuel or energy source (HS####). Example: “HS0001” (NATURAL GAS)

string

System configuration (HC####). Example: “HC0001” (CENTRAL)

string

Whether (and how completely) the building is heated, used when the source proves presence without naming the system (HX####).

object

Cooling system of the primary building. Per-building cooling is under buildingInformation.buildings[].cooling.

Show cooling properties

string

Cooling equipment (CL####); decode with the Property Feature Field Key. Example: “CL0001” (CENTRAL)

object

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.

Show buildingInformation properties

array of objects

List of all improved structures on the parcel, each with detailed appraisal characteristics from county assessor records.

example

"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
  }
]

Show building entry properties

integer

Building sequence number on the parcel (1 = primary building).

float

Assessed or appraised value of this building, also known as improvement value.

float

Number of stories in this building; half-stories are decimals (e.g., 1.5). Example: 2

float

Total heated/finished living area of this building in square feet. Example: 1628

float

Total building area in square feet; characteristics.buildingAreaType says what kind of measurement it represents. Example: 2348

array of objects

Breakdown of this building’s areas by section (e.g., ground floor, gross, garage, basement).

Show buildingAreas entry properties

float

Numeric area value in the units specified by areaUnits. Example: 2348

string

Unit of measure for area (e.g., “SF” for square feet, “LF” for linear feet). Example: “SF”

string

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. Example: “BA0003” (GROSS AREA)

float

The same measurement converted to square feet. Example: 2348

integer

Original year the building was constructed. Example: 1900

integer

Effective year built after renovations — reflects condition, not original construction. Example: 1967

integer

Number of bedrooms in this building. Example: 3

float

Total bathroom count in this building; half baths count as 0.5 (e.g., 2.5). Example: 2

integer

Number of full bathrooms (toilet + sink + tub/shower). Example: 2

integer

Number of half bathrooms (toilet + sink only). Example: 0

integer

Total plumbing fixture count for this building.

object

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.

object

This building’s heating system — identical facet set as the top-level heating object documented above (equipment, distribution, energySource, configuration, coverage).

object

This building’s cooling system — identical member set as the top-level cooling object documented above (equipment).

string

Roof framing type (e.g., “Truss”, “Rafter”). Not populated in the current data generation.

string

Floor structural system (e.g., “Joist”, “Slab on Grade”). Not populated in the current data generation.

string

Cabinet and millwork quality grade. Not populated in the current data generation.

string

Paint and decor quality grade. Not populated in the current data generation.

string

Bathroom tile quality or type. Not populated in the current data generation.

boolean

Whether the building has a pool; mirrors characteristics.pool.exists. Example: false

boolean

Whether the building has a fireplace.

integer

Number of fireplaces. Example: 2

boolean

Whether the building has a garage. Example: false

integer

Number of garage bays or spaces. Example: 0

Land, valuation, tax & legal

object

Aggregate land measurements, lot dimensions, and land classification for the parcel.

Show properties

number

Acreage as stated on the recorded deed.

number

Total parcel acreage from county assessor records. Example: 0.0425

number

Acreage calculated from GIS or survey data rather than stated on the deed.

number

Total land area in the units specified by landAreaUnits. Example: 1853

string

Unit of measure for totalLandArea (e.g., “AC” for acres, “SF” for square feet).

number

Lot depth in feet.

number

Lot frontage (street-facing width) in feet.

string

Site topography (TP#### — level, rolling, hilly, …); decode with the Property Feature Field Key. Example: “TP0001” (LEVEL GRADE)

string

Road access to the parcel (RA####); decode with the Property Feature Field Key. Vocabulary published; not yet populated in the current data generation.

string

Waterfront type (WF####); decode with the Property Feature Field Key. Vocabulary published; not yet populated in the current data generation.

string

View quality (VQ####); decode with the Property Feature Field Key. Vocabulary published; not yet populated in the current data generation.

array

Breakdown of the parcel into land segments by use code or soil class.

Show properties

string

Land use or soil classification code for this parcel segment. Not populated in the current data generation.

string

Soil productivity class or rating. Not populated in the current data generation.

number

Numeric area measurement for this land segment in the units specified by areaUnits.

string

Unit of measure for area (e.g., “AC”, “SF”, “FF”).

number

Area of this land segment in acres.

number

Area of this land segment in square feet.

number

Total assessed value of this land segment.

object

Assessor valuation figures and tax exemptions for the parcel.

Show properties

number

Total market value of the property (land plus buildings) from county assessor records. Example: 1184520

number

Total assessed value used for tax calculation. Example: 1184520

number

Assessed or appraised value of all buildings/improvements (also known as total improvement value). Example: 479530

number

Assessed or appraised value of the land only. Example: 704990

number

Total just/fair market value, used in Florida and similar jurisdictions.

number

Taxable value after exemptions are applied — the basis tax is actually levied against. Differs from totalAssessedValue when exemptions exist.

number

Tax year the assessment applies to. Example: 2025

number

Year the appraisal was performed.

array

Tax exemptions applied to the property.

Show properties

string

Exemption type as a readable value — no decode table needed. Values include “Homestead”, “Senior”, “Veteran”, “School/College”, “Disabled”, “Widow”, “Religious”. Example: “Homestead”

number

Dollar amount of the exemption.

string

Additional description or details about the exemption.

number

Total dollar value of all exemptions combined.

object

Tax amounts, districts, and historical tax records for the parcel.

Show properties

number

Total tax amount due or paid for the current tax year. Example: 59226

number

Tax year the record applies to. Example: 2025

string

Tax district name.

string

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”

string

Tax classification of the parcel (TC####); decode with the Property Feature Field Key. Vocabulary published; not yet populated in the current data generation.

string

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”

string

Tax-levying jurisdiction; may differ from the zoning jurisdiction.

string

URL to the county tax record or tax bill.

array

Historical tax records by year.

Show properties

number

Tax year this record applies to.

number

Total tax amount due or paid for that year.

string

Description of what the tax is for (e.g., “Property Tax”, “School Tax”, “Municipal Tax”).

string

Payment status (e.g., “Paid”, “Unpaid”, “Delinquent”, “Partial”).

string

Date the tax bill was paid.

string

Date the tax bill is or was due.

object

Recorded legal description, subdivision/plat identifiers, and Public Land Survey System references.

Show properties

string

Full legal description of the property as recorded. Example: “SQUARE 0314 LOT 0009 NBHD: OLD CITY 2”

string

Reference to the recorded legal document (e.g., deed book/page).

string

Name of the subdivision or plat. Example: “OLD CITY 2”

string

Public Land Survey System (PLSS) section number.

string

Public Land Survey System (PLSS) township designation.

string

Public Land Survey System (PLSS) range designation.

string

Block number within the subdivision plat. Example: “314”

string

Lot number within the block. Example: “9”

string

Lot composition of the legal parcel (LT#### — more than one lot, partial lot, …); decode with the Property Feature Field Key. Example: “LT0001” (MORE THAN ONE LOT)

string

Land lot number, used in metes-and-bounds states such as Georgia.

string

URL to the recorded deed document.

Sales history

array

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.

Show sales history entry properties

string

Date the sale was executed (YYYY-MM-DD format). Example: “2019-12-17”

string

Date the deed was recorded with the county (YYYY-MM-DD format). Example: “2020-01-16”

float

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

string

Combined deed book and page reference for the recorded instrument (e.g., “1234/567”).

string

Deed book number of the recorded instrument.

string

Deed page number of the recorded instrument.

string

Recorded instrument (deed) type on the event (TT####). Decode with the Property Feature Field Key. Example: “TT0001” (WARRANTY DEED)

string

Recorder’s document or instrument number for the sale. Mortgages that financed a sale reference this value via mortgages[].relatedSaleDocumentNumber. Example: “2020.6827”

string

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. In the v2-legacy flat shape this is exposed as transfers[].saleCode. Example: “TQ0002” (VALID ARM’S-LENGTH SALE)

boolean

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

string

Whether the property was vacant or improved at the time of sale. Not populated in the current data generation.

boolean

Whether the sale was distressed (foreclosure, short sale, etc.), as flagged in recorder records.

boolean

Whether the property was REO (bank-owned, post-foreclosure) at the time of sale, as flagged in recorder records.

float

Documentary transfer / excise tax paid on the sale, in dollars. Example: 0

string

Title company that handled the recorded transaction. Example: “ALLIED TITLE & ESCROW LLC”

string

Seller name in this transaction. Example: “MARR NELSON P”

string

Second seller/grantor name when the property was sold by co-sellers. Example: “MARR LISETTE M”

string

Buyer name in this transaction. Example: “6 TREE LLC”

string

Second buyer/grantee name when the property was bought by co-buyers.

string

What kind of entity the buyer is (BE#### — individual, company, trust, …). Decode with the Property Feature Field Key. Example: “BE0001” (INDIVIDUAL(S))

string

Relationship between co-buyers (BR####). Decode with the Property Feature Field Key. Example: “BR0001” (HUSBAND AND WIFE)

string

Legal role the buyer takes in the transfer (RO####). Decode with the Property Feature Field Key. Example: “RO0001” (BENEFICIARY/CREDITOR)

string

How the buyer holds title (BV#### — joint tenants, tenants in common, community property, …). Decode with the Property Feature Field Key. Example: “BV0001” (JOINT TENANTS)

string

How the recorded sale-price figure was obtained (PD#### — stated on the document, computed from transfer tax, …). Decode with the Property Feature Field Key. Example: “PD0001” (STATED ON DOCUMENT)

Mortgages, liens & foreclosures

array of objects

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.

example

"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"]
}
]

Show mortgage entry properties

float

Loan amount in dollars. Example: 308000

string

Lender / beneficiary name as recorded. Example: “AURORA FINANCIAL LLC”

float

Interest rate, in percent. Example: 4.0

string

Interest-rate structure (IR#### — fixed, variable, …). Decode with the Property Feature Field Key. Example: “IR0001” (VARIABLE RATE)

integer

Loan term length, in the unit given by termUnit. Example: 360

string

Unit of the loan term. Currently always “months”. Example: “months”

string

Loan product or program (LN####). Decode with the Property Feature Field Key. Example: “LN0001” (CONVENTIONAL LOAN)

string

Amortization structure (LA#### — balloon, …). Decode with the Property Feature Field Key. Example: “LA0001” (BALLOON)

string

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”

string

Date the mortgage was recorded (YYYY-MM-DD format). Example: “2017-03-21”

string

Recorder’s document number for the mortgage. Example: “2017.30971”

string

Loan maturity / due date (YYYY-MM-DD format). Example: “2047-04-01”

string

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”

string

What the loan financed (LX#### — purchase, refinance, construction, …). Decode with the Property Feature Field Key. Example: “LX0001” (REFINANCE / SECOND TRUST DEED)

boolean

Whether this loan is a refinance. Example: true

boolean

Whether this loan is a home equity line of credit. Example: true

boolean

Whether this loan is a home-equity loan. Example: true

boolean

Whether this loan is a construction loan.

boolean

Whether interestRate is estimated rather than recorded. Example: true

boolean

Whether the seller carried back financing.

boolean

Whether the lender is a private party rather than an institution.

boolean

Whether an adjustable-rate rider is present on the recorded mortgage. Example: true

string

Index the adjustable rate is tied to (RI####). Decode with the Property Feature Field Key. Example: “RI0001” (LIBOR 1-YEAR)

float

Lifetime maximum (cap) interest rate, in percent.

float

Lifetime minimum (floor) interest rate, in percent.

integer

Interest-only period length in months, if any.

number

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

integer

Year of the first scheduled rate change, as recorded (may appear as a two-digit year). Example: 24

array of strings

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. Example: [“RD0003”] (1-4 FAMILY RIDER)

array of objects

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.

Show assignment/release entry properties

string

“assignment” (the loan is transferred to a new holder) or “release” (the loan is satisfied/reconveyed). Example: “assignment”

string

Date this assignment/release was recorded (YYYY-MM-DD format). Example: “2025-01-21”

string

Lender assigning or releasing the loan (the current holder). Example: “CENTER STREET LENDING VIII SPE LLC”

string

Lender the loan is assigned to. Assignments only — absent for releases. Example: “CENTER STREET LENDING RIO IX LLC”

float

Original amount of the mortgage being assigned/released, in dollars. Example: 80000

string

Recording date of the original mortgage being assigned/released (YYYY-MM-DD format). Example: “2024-11-07”

string

Document number of the original mortgage being assigned/released. Example: “105276”

string

Recorder’s document number for this assignment/release record. Example: “6692”

string

Borrower on the underlying loan. Example: “6 TREE LLC”

array of objects

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.

Show lien entry properties

string

Type of the recorded lien or judgment (LI####). Decode with the Property Feature Field Key. Example: “LI0001” (FINANCING STATEMENT)

string

Date the lien was recorded (YYYY-MM-DD format).

string

Recorder’s document number for the lien.

float

Lien / judgment amount in dollars.

string

Lien holder / creditor — the party the lien is in favor of.

string

Debtor — the party the lien is against.

string

Court or case number associated with the lien, if any.

string

Document number of a related/referenced instrument (e.g., the underlying loan).

array of objects

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.

Show foreclosure entry properties

string

Type of the recorded foreclosure event (FR#### — lis pendens, notice of default, notice of sale, …). Decode with the Property Feature Field 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)

string

Date this foreclosure record was recorded (YYYY-MM-DD format).

string

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.

string

Recorder’s document number for this record.

string

Court or trustee case number.

string

Date of default (YYYY-MM-DD format).

float

Unpaid loan balance at filing, in dollars.

float

Amount past due at filing, in dollars.

string

Scheduled foreclosure-auction / trustee-sale date (YYYY-MM-DD format).

string

Scheduled auction time, as free text as recorded.

string

Scheduled auction location.

float

Minimum auction bid amount, in dollars.

string

Lender / beneficiary on the defaulted loan.

string

Trustee handling the foreclosure.

string

Borrower in default.

float

Original amount of the defaulted loan, in dollars.

Histories, valuation model & extensions

array

Historical appraised values by year from county assessor records — one entry per appraisal year, with land, building, and total market components.

Show appraisal entry properties

integer

Year of the appraisal. Example: 2024

float

Appraised value of buildings/improvements for this year (also known as improvement value).

float

Appraised value of land for this year.

float

Total appraised market value for this year.

array

Historical assessed values by year from county assessor records — one entry per assessment year, with land, building, total, and market components.

Show assessment entry properties

integer

Year of the assessment. Example: 2025

float

Assessed value of buildings/improvements for this year (also known as improvement value). Example: 479530

float

Assessed value of land for this year. Example: 704990

float

Total assessed value for this year. Example: 1184520

float

Market value recorded alongside the assessment for this year, where the county exposes both. Example: 1184520

integer

Year the market value applies to, when distinct from assessmentYear. Example: 2025

array

Building and construction permits associated with the property, sourced from the issuing jurisdiction’s permit records.

Show permit entry properties

string

Permit number or ID assigned by the issuing authority.

string

Authority that issued the permit (e.g. “City of Tampa”, “Hillsborough County”) — useful when permits cross municipal/county boundaries.

string

Short description of the permitted work.

string

Date the permit was issued (YYYY-MM-DD).

float

Estimated value of the permitted work as stated on the application.

string

Permit type (e.g., “Building”, “Electrical”, “Plumbing”, “Mechanical”).

string

Current status (e.g., “Issued”, “Final”, “Expired”, “Void”).

string

Date the permit application was submitted (YYYY-MM-DD).

string

Date the permit received final inspection/approval (YYYY-MM-DD).

string

Date the permit expires (YYYY-MM-DD).

string

Detailed description of the permitted work.

string

Licensed contractor name.

string

Contractor license number.

string

Contractor business address.

string

Contractor phone number.

float

Official valuation of the permitted work (may differ from the estimated value on the application).

float

Square footage affected by the permitted work.

integer

Number of stories affected by the permitted work.

integer

Number of units affected by the permitted work.

string

Most recent inspection status (e.g., “Passed”, “Failed”, “Pending”).

integer

Total number of inspections performed.

string

Date of the most recent inspection (YYYY-MM-DD).

float

Total permit fees charged in dollars.

string

Additional notes or comments on the permit.

string

URL to the permit record on the issuing jurisdiction’s site.

object

Electricity utility and rate information for the property’s service area.

Show utilityRateInfo properties

string

Name of the electric utility serving this property.

integer

EIA (U.S. Energy Information Administration) utility identifier.

string

Rate schedule name or code.

float

Default/Tier 1 residential rate in $/kWh.

float

Monthly fixed service charge in dollars.

string

Date the rate became effective (YYYY-MM-DD).

float

Estimated monthly consumption in kWh, derived from building square footage and type.

float

Estimated monthly electricity cost (rate × estimated kWh + fixed charge).

string

Rate data source: “urdb” (Utility Rate Database) or “scraped”.

string

URL where the rate data was sourced from.

object

The parcel’s zoning designation with provenance — the record’s one zoning surface. matchMethod says which of the two provenance tiers produced it.

Show zoningInfo properties

string

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.

string

Human-readable zoning description (e.g., “Single Family Residential”).

string

Regulatory body that administers the zoning (e.g., “HAMMOND”, “LAKE COUNTY”).

string

Identifier of the dataset the zoning designation was sourced from (e.g., “IN_LAKE_HAMMOND”).

string

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”

object

Availability flags and links for supplementary property resources — building sketches, property card PDFs, photos, and GIS maps.

Show additionalFeatures properties

boolean

Whether a building sketch/floor plan is available.

string

URL to the building sketch or floor plan document.

boolean

Whether the assessor property card PDF is available for download.

string

URL or reference to parcel photo(s).

boolean

Whether a GIS/parcel map is available.

string

URL to the GIS or parcel map viewer.

object

URLs to external property resources hosted by the county or its mapping providers.

Show externalLinks properties

string

URL to the county’s comparable sales search tool.

string

URL to the Pictometry/aerial photo viewer.

string

URL to the metro or county map viewer.

string

Catch-all for additional source data that does not fit the structured sections, serialized as a JSON string. Structure varies by county.

object

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).

Show realieValuation properties

object

Realie’s machine-learning AVM estimate. Produced for essentially all valued parcels.

Show ml properties

float

Calibrated ML point estimate of market value, in dollars.

float

Lower bound of the estimate band (30th percentile), in dollars.

float

Upper bound of the estimate band (70th percentile), in dollars.

float

Model ensemble disagreement, in dollars — larger values indicate a less certain estimate.

integer

Confidence tier from 0 to 100.

string

Confidence label: “very_high”, “high”, “medium”, “low”, or “very_low”.

string

Model version identifier for the estimate. Example: “v3-noassessor-2026-06-13”

object

Realie’s comparable-sales estimate — K-nearest recent comparable sales, no ML. Absent where comparable sales are too sparse.

Show comp properties

float

Comparable-sales point estimate (median comparable $/sqft × living area), in dollars.

float

Lower bound of the comp estimate band (25th percentile), in dollars.

float

Upper bound of the comp estimate band (75th percentile), in dollars.

float

Median price per square foot across the comparable sales used.

integer

Number of comparable sales used in the estimate.

float

Distance in miles to the farthest comparable used — a comp-density/confidence signal.

integer

Trailing lookback window for comparable sales, in months.

string

Comp-model version identifier for the estimate. Example: “compval-knn10-2026-06-13”

string

Date the valuation was scored (YYYY-MM-DD) — the “estimated as of” date.

object

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.

Show legacyDebtEstimate properties

integer

Modeled count of open liens against the parcel. Example: 2

float

Modeled total open lien balance in dollars. Example: 4377540

integer

Count of financing events in the legacy analytics model. Example: 8

float

Estimated current combined loan-to-value ratio, as a percentage. Example: 311.5685

integer

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

float

Estimated current owner equity in dollars (negative when modeled debt exceeds modeled value). Example: -2972539

integer

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

float

Loan-to-value ratio at purchase, as a percentage. Example: 75

string

Most recent lender name in the legacy debt model. Example: “CENTER STREET LENDING CORPORATION”

object

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.

Show legacyOwnershipSummary properties

string

Date the (v2-era) current ownership began (YYYYMMDD). Example: “20191217”

integer

Owner tenure at the property in months. Example: 72

integer

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

integer

Number of parcels held by the same owner, per the legacy owner match. Example: 12

integer

Residential parcels held by the same owner. Example: 10

integer

Commercial parcels held by the same owner. Example: 2

Get Started

Response Fields & Types

Property

Premium

Identity & location

Classification, utilities & rooms

Buildings

Land, valuation, tax & legal

Sales history

Mortgages, liens & foreclosures

Histories, valuation model & extensions

​Identity & location

​Classification, utilities & rooms

​Buildings

​Land, valuation, tax & legal

​Sales history

​Mortgages, liens & foreclosures

​Histories, valuation model & extensions

Identity & location

Classification, utilities & rooms

Buildings

Land, valuation, tax & legal

Sales history

Mortgages, liens & foreclosures

Histories, valuation model & extensions