PropertyLayer lists 3,141 available county products across all 50 states and the District of Columbia in the September 7, 2026 catalog snapshot. The dataset is sourced from county assessors, recorder offices, and GIS departments rather than modeled property attributes.Coverage and field presence still vary by county. Check the current PropertyLayer coverage directory or contact support@propertylayer.com before committing to a required geography or field.
PropertyLayer retains all parcel records, including ones with sparse data. Some competitors remove parcels that don’t meet a minimum field threshold, which artificially reduces their counts. A null field in PropertyLayer means the county didn’t provide that data, not that the parcel doesn’t exist.See Data fields for more on how null values work.
All data is obtained directly from county assessors, recorder offices, and GIS departments. PropertyLayer does not infer or derive parcel attributes. If a county doesn’t publish a field, it will be null in the API response rather than estimated.This approach ensures accuracy but means coverage completeness is dependent on each county’s data publishing practices.
Is the API really nationwide?
Yes. The API covers all US states and territories, and you never need to specify a state or region. Any location in the US uses the same endpoints. Individual counties may still be missing, in which case a lookup returns no results rather than an error.Which counties are missing?
Coverage changes as counties are onboarded. Contact support@propertylayer.com for the current status of the counties relevant to your use case.Can I get county-by-county coverage details?
Yes. Contact support@propertylayer.com and we can share a coverage breakdown for the specific counties relevant to your use case.
