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

> Property API response fields — v3 data generation

Explore the complete set of fields returned by the Realie Property API. Each field includes a name, type, and a brief explanation of its contents, helping you interpret and utilize the data effectively.

<Note>
  Fields with no value for a parcel are omitted from the response rather than returned as null. Persist `realieParcelId` as your property key — `_id` values are regenerated on each data load. Coded fields decode with the [Property Feature Field Key](/api-reference/v3/feature-key); if you are coming from v2, start with the [migration guide](/api-reference/v3/migration).
</Note>

<AccordionGroup>
  <Accordion title="Address & Parcel Data">
    <ResponseField name="realieParcelId" type="string">
      Stable Realie parcel identifier, persistent across data releases. Persist this — not `_id`, which is regenerated on each data load.
    </ResponseField>

    <ResponseField name="parcelId" type="string">
      Assessor's Parcel Number. Example: "R-3726-00C-0100-1"
    </ResponseField>

    <ResponseField name="state_parcelId" type="string">
      State abbreviation and parcel number joined. Example: "TX-R-3726-00C-0100-1"
    </ResponseField>

    <ResponseField name="state_parcelIdSTD" type="string">
      Standardized state/county parcel identifier, useful for matching parcels across sources.
    </ResponseField>

    <ResponseField name="address" type="string">
      Street number and street name. Example: "1234 JOHN ST"
    </ResponseField>

    <ResponseField name="addressFull" type="string">
      Full Address. Example: "1234 JOHN ST, PLANO, TX 75093"
    </ResponseField>

    <ResponseField name="addressFullUSPS" type="string">
      Full address in USPS-standardized form. Example: "1234 JOHN ST, PLANO, TX 75093"
    </ResponseField>

    <ResponseField name="fullAddress" type="string">
      Full address (alias of addressFull). Example: "1234 JOHN ST, PLANO, TX 75093"
    </ResponseField>

    <ResponseField name="addressFormal" type="string">
      Address in formal presentation formatting. Example: "1234 John St, Plano, TX 75093"
    </ResponseField>

    <ResponseField name="formattedAddress" type="string">
      Formatted address (alias of addressFormal). Example: "1234 John St, Plano, TX 75093"
    </ResponseField>

    <ResponseField name="addressLine1" type="string">
      Address line 1. Example: "1234 JOHN ST"
    </ResponseField>

    <ResponseField name="addressLine2" type="string">
      Address line 2 (unit, suite, etc.). Example: "APT 2B"
    </ResponseField>

    <ResponseField name="addressRaw" type="string">
      Address as delivered by the county source, prior to normalization.
    </ResponseField>

    <ResponseField name="street" type="string">
      Street name and street type. Example: "JOHN ST"
    </ResponseField>

    <ResponseField name="streetName" type="string">
      Street name without the street type. Example: "JOHN"
    </ResponseField>

    <ResponseField name="streetType" type="string">
      Street type abbreviation. Example: "RD"
    </ResponseField>

    <ResponseField name="streetNumber" type="string">
      Street Number. Example: "1234"
    </ResponseField>

    <ResponseField name="streetDirectionPrefix" type="string">
      Directional prefix of the street. Example: "N"
    </ResponseField>

    <ResponseField name="streetDirectionSuffix" type="string">
      Directional suffix of the street. Example: "SW"
    </ResponseField>

    <ResponseField name="unitNumber" type="string">
      Unit Number. Example: "APT 2B"
    </ResponseField>

    <ResponseField name="unitNumberStripped" type="string">
      Unit Number. Example: "2B"
    </ResponseField>

    <ResponseField name="addressUnit" type="string">
      The address with a unit at the end. Example: "1234 JOHN ST APT 2B"
    </ResponseField>

    <ResponseField name="county" type="string">
      County the parcel is located in. Example: "COLLIN"
    </ResponseField>

    <ResponseField name="city" type="string">
      City. Example: "PLANO"
    </ResponseField>

    <ResponseField name="cityUSPS" type="string">
      USPS-preferred city name. Example: "PLANO"
    </ResponseField>

    <ResponseField name="zipCode" type="string">
      Zip Code. Example: "75093"
    </ResponseField>

    <ResponseField name="zipCodePlusFour" type="string">
      ZIP+4 code. Example: "75093-4351"
    </ResponseField>

    <ResponseField name="state" type="string">
      State. Example: "TX"
    </ResponseField>
  </Accordion>

  <Accordion title="Physical Characteristics Data">
    <ResponseField name="buildingArea" type="float">
      Building Area. Example: 5882
    </ResponseField>

    <ResponseField name="livingArea" type="float">
      Finished living area in square feet. Example: 4200
    </ResponseField>

    <ResponseField name="realieSquareFootage" type="float">
      Square footage used internally by the Realie valuation models. Not returned by the public API.
    </ResponseField>

    <ResponseField name="basementType" type="string">
      Basement Type. Example: "E". Codes changed from v2 — see the [Property Feature Field Key](/api-reference/v3/feature-key).
    </ResponseField>

    <ResponseField name="wallType" type="string">
      Wall Type. Example: "F". Codes changed from v2 — see the [Property Feature Field Key](/api-reference/v3/feature-key).
    </ResponseField>

    <ResponseField name="fireplaceCount" type="integer">
      Fireplace Count. Example: 2
    </ResponseField>

    <ResponseField name="fireplace" type="boolean">
      Identifying if the property has a fireplace. Example: true
    </ResponseField>

    <ResponseField name="floorType" type="string">
      Floor Type. Example: "L". Codes changed from v2 — see the [Property Feature Field Key](/api-reference/v3/feature-key).
    </ResponseField>

    <ResponseField name="foundationType" type="string">
      Foundation Type. Values are currently absent — the new data source carries no foundation data today; previously delivered values may be restored in a future release as archived data.
    </ResponseField>

    <ResponseField name="garageCount" type="integer">
      Garage Count. Example: 2
    </ResponseField>

    <ResponseField name="garage" type="boolean">
      Identifying if the property has a garage. Example: true
    </ResponseField>

    <ResponseField name="garageType" type="string">
      Garage Type. Example: "A". Codes changed from v2 — see the [Property Feature Field Key](/api-reference/v3/feature-key).
    </ResponseField>

    <ResponseField name="airConditioning" type="boolean">
      Identifying if the property has air conditioning. Example: true
    </ResponseField>

    <ResponseField name="buildingCount" type="integer">
      Building Count. Example: 1
    </ResponseField>

    <ResponseField name="roomCount" type="integer">
      Total room count. Example: 9
    </ResponseField>

    <ResponseField name="unitCount" type="integer">
      Number of units on the parcel. Example: 1
    </ResponseField>

    <ResponseField name="stories" type="float">
      Stories. Example: 2
    </ResponseField>

    <ResponseField name="totalBathrooms" type="float">
      Total Bathrooms. Decimal — fractional counts (e.g. 2.5) are real JSON numbers (v2 delivered truncated integers). Example: 3.5
    </ResponseField>

    <ResponseField name="fullBathrooms" type="float">
      Full bathroom count. Example: 3
    </ResponseField>

    <ResponseField name="halfBathrooms" type="float">
      Half bathroom count. Example: 1
    </ResponseField>

    <ResponseField name="totalBedrooms" type="integer">
      Total Bedrooms. Example: 5
    </ResponseField>

    <ResponseField name="pool" type="boolean">
      Identifying if property has a pool. Example: true
    </ResponseField>

    <ResponseField name="poolCode" type="string">
      Pool type code. Example: "E". Codes changed from v2 — see the [Property Feature Field Key](/api-reference/v3/feature-key).
    </ResponseField>

    <ResponseField name="roofType" type="string">
      Roof Type (material). Example: "H". Codes changed from v2 — see the [Property Feature Field Key](/api-reference/v3/feature-key).
    </ResponseField>

    <ResponseField name="roofStyle" type="string">
      Roof Style (shape). Example: "E". Codes changed from v2 — see the [Property Feature Field Key](/api-reference/v3/feature-key).
    </ResponseField>

    <ResponseField name="constructionType" type="string">
      Construction Type. Example: "G". Codes changed from v2 — see the [Property Feature Field Key](/api-reference/v3/feature-key).
    </ResponseField>

    <ResponseField name="styleDesc" type="string">
      Building style description. Example: "RANCH"
    </ResponseField>

    <ResponseField name="conditionDesc" type="string">
      Building condition description. Example: "AVERAGE"
    </ResponseField>

    <ResponseField name="gradeDesc" type="string">
      Building quality/grade description. Example: "GOOD"
    </ResponseField>

    <ResponseField name="yearBuilt" type="integer">
      Year Built. Example: 1998
    </ResponseField>

    <ResponseField name="effectiveYearBuilt" type="integer">
      Effective year built, reflecting renovations. Example: 2005
    </ResponseField>

    <ResponseField name="residential" type="boolean">
      Identifying if the property is residential. Example: true
    </ResponseField>

    <ResponseField name="condo" type="boolean">
      Identifying if the property is a condominium. Example: false
    </ResponseField>
  </Accordion>

  <Accordion title="Ownership Data">
    <ResponseField name="ownerName" type="string">
      Property owner's name, as delivered by the county (raw `LAST FIRST` string). Example: "DOE JOHN"
    </ResponseField>

    <ResponseField name="ownerName2" type="string">
      Second owner's name, as delivered by the county (raw `LAST FIRST` string). Example: "DOE JANE"
    </ResponseField>

    <ResponseField name="ownerAddressLine1" type="string">
      Owner Address Line 1. Example: "4567 JOHN DR"
    </ResponseField>

    <ResponseField name="mailerAddress" type="string">
      Owner mailing street address (alias of ownerAddressLine1). Example: "4567 JOHN DR"
    </ResponseField>

    <ResponseField name="ownerAddressFull" type="string">
      Owner's full mailing address. Example: "4567 JOHN DR, PLANO, TX 75093"
    </ResponseField>

    <ResponseField name="ownerCity" type="string">
      Owner City. Example: "PLANO"
    </ResponseField>

    <ResponseField name="mailingCity" type="string">
      Owner mailing city (alias of ownerCity). Example: "PLANO"
    </ResponseField>

    <ResponseField name="ownerState" type="string">
      Owner State. Example: "TX"
    </ResponseField>

    <ResponseField name="mailingState" type="string">
      Owner mailing state (alias of ownerState). Example: "TX"
    </ResponseField>

    <ResponseField name="ownerZipCode" type="string">
      Owner Zip Code. Example: "75093"
    </ResponseField>

    <ResponseField name="mailingZip5" type="string">
      Owner mailing ZIP (alias of ownerZipCode). Example: "75093"
    </ResponseField>

    <ResponseField name="ownerZipCodePlusFour" type="string">
      Owner ZIP+4 extension. Example: "4351"
    </ResponseField>

    <ResponseField name="mailingZip4" type="string">
      Owner mailing ZIP+4 extension (alias of ownerZipCodePlusFour). Example: "4351"
    </ResponseField>

    <ResponseField name="ownerResCount" type="integer">
      Owner Residential Count. Frozen estimate captured May 2026; does not refresh with data releases. Example: 1
    </ResponseField>

    <ResponseField name="ownerComCount" type="integer">
      Owner Commercial Count. Frozen estimate captured May 2026; does not refresh with data releases. Example: 0
    </ResponseField>

    <ResponseField name="ownerOriginCode" type="string">
      Owner Origin Code. Frozen estimate captured May 2026; does not refresh with data releases. Example: "3"
    </ResponseField>

    <ResponseField name="ownerParcelCount" type="integer">
      Owner Parcel Count. Frozen estimate captured May 2026; does not refresh with data releases. Example: 1
    </ResponseField>

    <ResponseField name="lengthOfResidenceMonths" type="integer">
      Months the current owner has held the property. Frozen estimate captured May 2026; does not refresh with data releases. Example: 38
    </ResponseField>

    <ResponseField name="lengthOfResidenceCode" type="string">
      Coded length-of-residence band. Frozen estimate captured May 2026; does not refresh with data releases.
    </ResponseField>
  </Accordion>

  <Accordion title="Land Details & Zoning Data">
    <ResponseField name="legalDesc" type="string">
      Legal Description. Example: "CITY/MUNI/TWP:PLANO CITY WILLOW BEND POLO ESTATES PHASE G (CPL), BLK C, LOT 10"
    </ResponseField>

    <ResponseField name="legalDescription" type="string">
      Legal description (alias of legalDesc). Example: "CITY/MUNI/TWP:PLANO CITY WILLOW BEND POLO ESTATES PHASE G (CPL), BLK C, LOT 10"
    </ResponseField>

    <ResponseField name="subdivision" type="string">
      Subdivision. Example: "WILLOW BEND POLO ESTATES PHASE G (CPL)"
    </ResponseField>

    <ResponseField name="zoningCode" type="string">
      Zoning Code. Example: "RD-5"
    </ResponseField>

    <ResponseField name="blockNum" type="string">
      Block Number. Example: "C"
    </ResponseField>

    <ResponseField name="blockNumber" type="string">
      Block number (alias of blockNum). Example: "C"
    </ResponseField>

    <ResponseField name="lotNum" type="string">
      Lot Number. Example: "10"
    </ResponseField>

    <ResponseField name="lotNumber" type="string">
      Lot number (alias of lotNum). Example: "10"
    </ResponseField>

    <ResponseField name="section" type="string">
      Public Land Survey System section. Example: "3"
    </ResponseField>

    <ResponseField name="township" type="string">
      Public Land Survey System township. Example: "3N"
    </ResponseField>

    <ResponseField name="range" type="string">
      Public Land Survey System range. Example: "9W"
    </ResponseField>

    <ResponseField name="landLot" type="string">
      Land Lot. Example: "Lot 5"
    </ResponseField>

    <ResponseField name="lotCode" type="string">
      Lot Code. Example: "D". Codes changed from v2 — see the [Property Feature Field Key](/api-reference/v3/feature-key).
    </ResponseField>

    <ResponseField name="acres" type="float">
      Acres. Example: 0.32
    </ResponseField>

    <ResponseField name="depthSize" type="float">
      Depth Size. Example: 150
    </ResponseField>

    <ResponseField name="depth" type="float">
      Lot depth (alias of depthSize). Example: 150
    </ResponseField>

    <ResponseField name="frontage" type="float">
      Frontage. Example: 100
    </ResponseField>

    <ResponseField name="landArea" type="float">
      Land Area. Example: 14096
    </ResponseField>

    <ResponseField name="lotSizeArea" type="float">
      Lot size area (alias of landArea). Example: 14096
    </ResponseField>
  </Accordion>

  <Accordion title="Automated Valuation Model (AVM) & Tax Data">
    <ResponseField name="totalAssessedValue" type="float">
      Most recent total assessed value. Example: 1669610
    </ResponseField>

    <ResponseField name="assessedYear" type="integer">
      Most recent assessed year. Example: 2024
    </ResponseField>

    <ResponseField name="taxValue" type="float">
      Most recent property tax amount. Example: 17642.22
    </ResponseField>

    <ResponseField name="taxYear" type="integer">
      Most recent property tax year. Example: 2024
    </ResponseField>

    <ResponseField name="totalBuildingValue" type="float">
      Most recent assessed total building value. Example: 400110
    </ResponseField>

    <ResponseField name="totalLandValue" type="float">
      Most recent assessed land value. Example: 269500
    </ResponseField>

    <ResponseField name="totalMarketValue" type="float">
      Most recent assessed market value. Example: 1669610
    </ResponseField>

    <ResponseField name="marketValueYear" type="integer">
      Most recent assessed market value year. Example: 2024
    </ResponseField>

    <ResponseField name="taxRateCodeArea" type="string">
      Tax Rate Code Area. Example: "GCN"
    </ResponseField>

    <ResponseField name="useCode" type="string">
      Parcel's Use Code. Same 4-digit scheme as v2 (a small number of v2-era codes are retired and re-coded to specific successors — see the [migration guide](/api-reference/v3/migration)). Decode with the [Property Feature Field Key](/api-reference/v3/feature-key). Example: "1001"
    </ResponseField>

    <ResponseField name="modelValue" type="float">
      Model Value. Example: 1739895
    </ResponseField>

    <ResponseField name="modelValueMin" type="float">
      Model Value Minimum. Example: 1496309
    </ResponseField>

    <ResponseField name="modelValueMax" type="float">
      Model Value Maximum. Example: 1983480
    </ResponseField>

    <ResponseField name="modelValueStdDev" type="float">
      Model value standard deviation. Not returned by the public API.
    </ResponseField>

    <ResponseField name="modelValueRange" type="float">
      Spread between modelValueMax and modelValueMin. Not returned by the public API.
    </ResponseField>

    <ResponseField name="modelConfidence" type="float">
      Model confidence signal. Not returned by the public API.
    </ResponseField>

    <ResponseField name="modelConfidenceBucket" type="string">
      Model confidence tier. Not returned by the public API.
    </ResponseField>

    <ResponseField name="modelDate" type="date">
      Date the model value was produced. Not returned by the public API.
    </ResponseField>

    <ResponseField name="modelVersion" type="string">
      Version of the model behind modelValue.
    </ResponseField>

    <ResponseField name="compModelValue" type="float">
      Comparable-sales model value estimate. Example: 1712000
    </ResponseField>

    <ResponseField name="compModelValueMin" type="float">
      Comparable-sales model value minimum. Example: 1540800
    </ResponseField>

    <ResponseField name="compModelValueMax" type="float">
      Comparable-sales model value maximum. Example: 1883200
    </ResponseField>

    <ResponseField name="compPpsf" type="float">
      Price per square foot behind the comparable-sales estimate. Example: 407.62
    </ResponseField>

    <ResponseField name="compCount" type="integer">
      Number of comparable sales used. Example: 12
    </ResponseField>

    <ResponseField name="compMaxDistMi" type="float">
      Maximum distance of the comparables used, in miles. Example: 1.5
    </ResponseField>

    <ResponseField name="compWindowMo" type="integer">
      Look-back window of the comparables used, in months. Example: 12
    </ResponseField>

    <ResponseField name="compModelVersion" type="string">
      Version of the comparable-sales model.
    </ResponseField>

    <ResponseField name="estimateAgreementPct" type="float">
      Relative difference between modelValue and compModelValue (0 = identical estimates). Example: 0.04
    </ResponseField>

    <ResponseField name="assessments" type="array of objects">
      Array of assessment information from previous years.

      ```json example theme={null}
       "assessments": [
             {
                 "assessedYear": 2023,
                 "totalAssessedValue": 3072135,
                 "totalBuildingValue": 2572135,
                 "totalLandValue": 500000,
                 "totalMarketValue": 4072135,
                 "marketValueYear": 2023,
                 "taxValue": 34435.7,
                 "taxYear": 2023
             }
      ]
      ```

      <Expandable title="assessment entry properties">
        <ResponseField name="assessedYear" type="integer">
          Assessment year this entry covers. Example: 2023
        </ResponseField>

        <ResponseField name="totalAssessedValue" type="float">
          Total assessed value for this assessment year. Example: 3072135
        </ResponseField>

        <ResponseField name="totalBuildingValue" type="float">
          Assessed building value for this assessment year. Example: 2572135
        </ResponseField>

        <ResponseField name="totalLandValue" type="float">
          Assessed land value for this assessment year. Example: 500000
        </ResponseField>

        <ResponseField name="totalMarketValue" type="float">
          Assessed market value for this entry. Example: 4072135
        </ResponseField>

        <ResponseField name="marketValueYear" type="integer">
          Year the market value applies to. Example: 2023
        </ResponseField>

        <ResponseField name="taxValue" type="float">
          Property tax amount for this entry. Example: 34435.7
        </ResponseField>

        <ResponseField name="taxYear" type="integer">
          Tax year the tax amount applies to. Example: 2023
        </ResponseField>
      </Expandable>
    </ResponseField>
  </Accordion>

  <Accordion title="Transfer & Recording Data">
    <ResponseField name="recordingDate" type="string">
      Recording Date (YYYY-MM-DD format). Example: "2024-01-10"
    </ResponseField>

    <ResponseField name="transferDate" type="string">
      Transfer Date (YYYY-MM-DD format). Example: "2024-01-05"
    </ResponseField>

    <ResponseField name="transferDateObject" type="date">
      Transfer date in ISO 8601 format. Example: "2024-01-05T00:00:00.000Z"
    </ResponseField>

    <ResponseField name="transferPrice" type="float">
      Transfer Price. Example: 525000
    </ResponseField>

    <ResponseField name="grantee" type="string">
      Buyer (grantee) on the latest sale. Example: "SMITH, JOHN"
    </ResponseField>

    <ResponseField name="qualified" type="boolean">
      Boolean qualification of the latest sale; also carried per event on transfers\[]. Absent on nearly all events recorded after March 2026 — prefer transfers\[].saleCode for qualification semantics on recent events. Example: true
    </ResponseField>

    <ResponseField name="buyerIDCode" type="string">
      Who the buyers are to each other (their personal relationship), for reporting / tax eligibility purposes. Example: "13". Codes changed from v2 — see the [Property Feature Field Key](/api-reference/v3/feature-key).
    </ResponseField>

    <ResponseField name="bookNum" type="string">
      The volume identifier assigned by the county recorder that indicates which official record book a real estate transaction document (such as a deed) is stored in.
    </ResponseField>

    <ResponseField name="pageNum" type="string">
      The specific page within that book where the recorded real estate transaction document begins.
    </ResponseField>

    <ResponseField name="buyerVestingCode" type="string">
      How the buyers legally hold title to the property. Example: "60" (LIMITED LIABILITY COMPANY / PARTNERSHIP). Codes changed from v2 — see the [Property Feature Field Key](/api-reference/v3/feature-key).
    </ResponseField>

    <ResponseField name="distressedSale" type="integer">
      Flag (0/1) identifying the latest sale as a distressed sale. Example: 0
    </ResponseField>

    <ResponseField name="realEstateOwnedPurchaseSale" type="integer">
      Flag (0/1) identifying the latest sale as a real-estate-owned (REO) purchase. Example: 0
    </ResponseField>

    <ResponseField name="ownershipStartDate" type="string">
      Date current owner took possession of the property (YYYY-MM-DD format). Frozen estimate captured May 2026; does not refresh with data releases. Example: "2023-05-05"
    </ResponseField>

    <ResponseField name="transferDocType" type="string">
      The document type that transfers property ownership from a grantor to a grantee. Decode with the [Property Feature Field Key](/api-reference/v3/feature-key); a small share of records (\~2%) carry numeric source codes that will be folded into named codes in an upcoming release. Example: "WD" (WARRANTY DEED)
    </ResponseField>

    <ResponseField name="transferDocNum" type="string">
      Reference number for the transfer document. Example: "2023R0119502"
    </ResponseField>

    <ResponseField name="transfers" type="array of objects">
      Array of the property's sale/transfer events, sorted newest-first. Each entry carries up to 11 keys — a key is absent when the source record has no value. The flat latest-sale fields (transferDate, transferPrice, and the other latest-sale scalars) are always derived from the newest dated entry of this array.

      ```json example theme={null}
      "transfers": [
      {
                "transferDate": "2016-04-27",
                "transferDateObject": "2016-04-27T00:00:00.000Z",
                "transferPrice": 2700000,
                "recordingDate": "2016-05-05",
                "transferDocNum": "2016R0045102",
                "transferDocType": "WD",
                "bookNum": "1234",
                "pageNum": "56",
                "grantee": "SMITH, JOHN",
                "qualified": true,
                "saleCode": "TQ0022"
      }
      ]
      ```

      <Expandable title="transfer entry properties">
        <ResponseField name="transferDate" type="string">
          Date the sale was executed (YYYY-MM-DD format). Example: "2016-04-27"
        </ResponseField>

        <ResponseField name="transferDateObject" type="date">
          The same instant as transferDate, in ISO 8601 timestamp form. Example: "2016-04-27T00:00:00.000Z"
        </ResponseField>

        <ResponseField name="transferPrice" type="float">
          Recorded sale price for this event. Absent in non-disclosure situations, where no price is recorded. Example: 2700000
        </ResponseField>

        <ResponseField name="recordingDate" type="string">
          Date the county recorded the document (YYYY-MM-DD format). Example: "2016-05-05"
        </ResponseField>

        <ResponseField name="transferDocNum" type="string">
          Recorder document (instrument) number for this event. Example: "2016R0045102"
        </ResponseField>

        <ResponseField name="transferDocType" type="string">
          Deed/instrument type code for this event. Decode with the [Property Feature Field Key](/api-reference/v3/feature-key). Example: "WD" (WARRANTY DEED)
        </ResponseField>

        <ResponseField name="bookNum" type="string">
          Official record book the recorded document is stored in. Example: "1234"
        </ResponseField>

        <ResponseField name="pageNum" type="string">
          Page within that book where the recorded document begins. Example: "56"
        </ResponseField>

        <ResponseField name="grantee" type="string">
          Buyer (grantee) name as recorded, in LAST FIRST convention. Example: "SMITH, JOHN"
        </ResponseField>

        <ResponseField name="qualified" type="boolean">
          Sale-qualification boolean carried on the source record. Absent on nearly all events recorded after March 2026 — prefer saleCode for qualification semantics on recent events. Example: true
        </ResponseField>

        <ResponseField name="saleCode" type="string">
          Realie sale-qualification code (`TQ####`). Codes changed from v2 — decode with the [Property Feature Field Key](/api-reference/v3/feature-key). Example: "TQ0022" (VALID ARM'S-LENGTH SALE)
        </ResponseField>
      </Expandable>
    </ResponseField>
  </Accordion>

  <Accordion title="Mortgage & Lien Data">
    <ResponseField name="totalLienCount" type="integer">
      Total Lien Count. Computed from recorded lien records when lien data is known for the parcel (a known-empty set counts as zero); otherwise a frozen estimate captured May 2026. Example: 1
    </ResponseField>

    <ResponseField name="totalLienBalance" type="float">
      Total Lien Balance. Computed from recorded lien records when lien data is known for the parcel (a known-empty set counts as zero); otherwise a frozen estimate captured May 2026. Example: 453664
    </ResponseField>

    <ResponseField name="totalFinancingHistCount" type="integer">
      Total Financing History Count. Frozen estimate captured May 2026; does not refresh with data releases. Example: 5
    </ResponseField>

    <ResponseField name="LTVCurrentEstCombined" type="float">
      Loan-to-Value Current Estimate. Frozen estimate captured May 2026; does not refresh with data releases. Example: 26.0742
    </ResponseField>

    <ResponseField name="LTVCurrentEstRange" type="float">
      Loan-to-Value Current Estimate Range. Frozen estimate captured May 2026; does not refresh with data releases. Example: 1
    </ResponseField>

    <ResponseField name="equityCurrentEstBal" type="float">
      Equity Current Estimate Balance. Frozen estimate captured May 2026; does not refresh with data releases. Example: 1286231
    </ResponseField>

    <ResponseField name="equityCurrentEstRange" type="float">
      Equity Current Estimate Range. Frozen estimate captured May 2026; does not refresh with data releases. Example: 22
    </ResponseField>

    <ResponseField name="LTVPurchase" type="float">
      Loan-to-Value Purchase. Frozen estimate captured May 2026; does not refresh with data releases. Example: 80
    </ResponseField>

    <ResponseField name="lenderName" type="string">
      Lender Name. From the most recent recorded mortgage when mortgage data is known for the parcel (omitted if that record carries no lender name); otherwise a frozen estimate captured May 2026. Example: "FIRST NATIONAL BANK"
    </ResponseField>

    <ResponseField name="forecloseCode" type="string">
      Foreclosure Code. Example: "NOD". Codes changed from v2 — see the [Property Feature Field Key](/api-reference/v3/feature-key).
    </ResponseField>

    <ResponseField name="forecloseRecordDate" type="string">
      Foreclosure Record Date (YYYY-MM-DD format). Example: "2024-01-10"
    </ResponseField>

    <ResponseField name="forecloseCaseNum" type="string">
      Foreclosure Case Number. Example: "722324"
    </ResponseField>

    <ResponseField name="auctionDate" type="string">
      Auction Date (YYYY-MM-DD format). Example: "2024-01-10"
    </ResponseField>
  </Accordion>

  <Accordion title="Location Data">
    <ResponseField name="fipsState" type="string">
      FIPS State Code. Example: "48"
    </ResponseField>

    <ResponseField name="fipsCounty" type="string">
      FIPS County Code. Example: "085"
    </ResponseField>

    <ResponseField name="siteCensusTract" type="string">
      Site Census Tract. Example: "480850316.682028"
    </ResponseField>

    <ResponseField name="neighborhood" type="string">
      Neighborhood. Example: "CENTRAL PLANO"
    </ResponseField>

    <ResponseField name="longitude" type="float">
      Longitude. Example: -96.8229693260567
    </ResponseField>

    <ResponseField name="latitude" type="float">
      Latitude. Example: 33.03128999789361
    </ResponseField>

    <ResponseField name="location" type="geojson">
      Geojson point object.

      ```json example theme={null}
      "location": {
            "type": "Point",
            "coordinates": [
                -121.88081453613906,
                36.52594926758319
            ]
        }
      ```
    </ResponseField>

    <ResponseField name="geometry" type="geojson">
      Geojson MultiPolygon showing a property's parcel polygon

      ```json example theme={null}
      "geometry": {
      "type": "MultiPolygon",
      "coordinates": [
       [
         [
           [-88.0153597, 42.0000236],
           [-88.0153815, 42.0003284],
           [-88.0156542, 42.0003187],
           [-88.0156365, 42.0000141],
           [-88.0155919, 42.0000157],
           [-88.015467, 42.0000199],
           [-88.0153597, 42.0000236]
         ]
       ]
      ]
      }
      ```
    </ResponseField>
  </Accordion>
</AccordionGroup>
