includeExplicitNulls=true to receive every field, with null where the parcel has no value. Store realieId as your property key: it stays the same when the county renumbers the parcel and we link the new number to it (see Availability and limits). Don’t key on realieParcelId, which follows the county’s current parcel number, or on _id, which API responses in the v3 shape do not carry.
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
Primary parcel identifier (Assessor’s Parcel Number / tax map parcel ID) as recorded by the county assessor. Example: “0314- -0009”
Realie parcel identifier built from the county’s parcel number. Format: 5-digit county FIPS + the parcel ID with spaces escaped as
~. When the county renumbers the parcel, realieParcelId changes and the former value moves to parcelIdHistory, so key on realieId instead. Example: “11001-0314-~-0009”The parcel’s permanent Realie id: 24 hexadecimal characters. It stays the same when the county renumbers the parcel and we link the new number to it — store it as your property key. Pass it as
realieId to Parcel ID Lookup to fetch this parcel. Example: “6650f1c2a1b2c3d4e5f60718”The parcel’s former numbers, oldest first: one entry for each renumbering we recorded (we record them from October 30, 2026). Omitted when we have recorded none. Parcel ID Lookup still finds the parcel by a former number. Example:
[{ "realieParcelId": "11001-0298-~-0815", "parcelId": "0298- -0815", "changedOn": "2026-07-01", "reason": "renumbered" }]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. Example: “1110”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.906297Longitude of the parcel centroid in decimal degrees (mirrors
coordinates.longitude). Omitted when the parcel has no valid geocode. Example: -77.027766GeoJSON 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] }Parcel boundary as a GeoJSON MultiPolygon (single-polygon boundaries are wrapped to MultiPolygon). Omitted when no boundary was matched for the parcel — see
geometrySource.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”Physical (situs) address of the parcel. The owner mailing address lives in
propertyIdentification.currentOwner.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.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.Property-level room totals across all buildings. Per-building room counts are in
buildingInformation.buildings (totalBedrooms, totalBathrooms, etc.).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.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. The same member set appears per building under
buildingInformation.buildings[].characteristics.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.Cooling system of the primary building. Per-building cooling is under
buildingInformation.buildings[].cooling.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.Land, valuation, tax & legal
Recorded legal description, subdivision/plat identifiers, and Public Land Survey System references.
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. An entry can record a package sale: one deed that conveyed several parcels, whose salePrice is the total for all of them (see multiParcel below).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.
example
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.
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.
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.
Historical assessed values by year from county assessor records — one entry per assessment year, with land, building, total, and market components.
Building and construction permits associated with the property, sourced from the issuing jurisdiction’s permit records.
The parcel’s zoning designation with provenance — the record’s one zoning surface.
matchMethod says which of the two provenance tiers produced it.Availability flags and links for supplementary property resources — building sketches, property card PDFs, photos, and GIS maps.
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).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.
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.