Real-time unit-level data integrating property attributes with sales, listing, and rental events in a single, clean response
Overview
Prior to Parcl Labs, property-level data was scattered across siloed, incompatible sources. No single provider offered complete coverage of markets and housing events. This made it difficult to track a unit's history across sales, listings, and rentals without extensive data aggregation and engineering efforts.
Parcl Labs solves this problem. We've integrated data from many sales, listing, and rental sources to create comprehensive unit-level histories covering the entire property lifecycle. Just as we use parcl_ids for our unique market-level indexing, at the unit level we use parcl_property_ids. This indexing system ties all housing events to a specific property.
Our approach offers:
- Clean event histories for every U.S. residential unit
- Daily updates
- An intuitive API that lets you precisely select the units you want to analyze
Parcl Labs’ property-level endpoints make this data accessible at the most granular level: the individual unit.
Property Data Coverage
Category | Coverage |
|---|---|
Property Types | ✅ Single Family ✅ Townhouses ✅ Condos ✅ Other |
Markets | 🇺🇸 All US Markets |
Housing Events | Granular events captured at each stage of the property lifecycle, indexed at the unit level: ✅ Sales → Sold, Non Arms Length Transfer, Inter Portfolio Transfer, Intra Portfolio Transfer ✅ For Sale Listings → Listed for Sale, Listing Removed, Other, Pending Sale, Price Change, Relisted ✅ Rentals → Listed for Rent, Price Change, Delisted for Rent Property and ownership insights at the event: 🏛️ Investor and True Entity Ownership 🏗️ New Construction Status |
Property Attributes | Accurate and standardized attributes about the property’s location and physical details:
|
Refresh Frequency | ✅ Daily |
History | January 2010-Current |
Available Property Endpoints
Parcl Labs provides two main ways to get property data: search all properties that match your criteria (by location, property attributes, ownership, event criteria, etc.) or search by address.
The property endpoints are extremely flexible, letting you target the exact properties and events you need. Whether you're looking for a needle in the haystack - the 1 property that meets your highly targeted filters - or bulk downloading all properties within a large metro area, Parcl Labs' endpoints make it simple and fast.
Gets list of properties and their housing event history based on user-defined search parameters.
This endpoint supports three search methods:
- parcl_property_ids (specific properties)
- parcl_ids (markets)
- geo_coordinates (latitude and longitude)
Additional search filters include property attributes, owners, and events.
Use Property Search V2 when you need to find properties that match your specific criteria - whether by market, ownership, property characteristics, or event history. Returns a list of properties with their parcl_property_ids, key attributes, and events.
Example Queries:
- Get all 3-bedroom units in zip code 12345
- Get all units currently on market for sale under $500,000 in Chicago
- Get all units currently owned by Invitation Homes in Atlanta that were built after 2020 and their rental performance history
- Get all new construction properties in Austin that have had a price cut
Review the Property Search endpoint documentation for the complete list of request parameters and example response data.
Search for a specific address to retrieve its corresponding parcl_property_id, location details, physical attributes, and current ownership insights. The parcl_property_id is key for navigating the Parcl Labs API, serving as the core mechanism for retrieving detailed property-level information in other property endpoints.
Use Search Address when you need to convert known specific addresses into parcl_property_ids to access data about individual properties. Use cases include:
- Process user-inputted addresses in your application
- Retrieve data for properties in your portfolio
- Validate address accuracy in your database
- Fetch data for a single property
Example Queries:
- Get parcl_property_id for 123 Main St, Anytown, USA
Review the Address Search endpoint documentation for example response data. You can learn more about our address resolution process here.
Note: Property V1 endpoints (search and events) are available and fully supported. We recommend migrating to the Property V2 endpoint as it provides the most efficient and flexible property data experience.
Get Started with Property-Level Data
To get started, check out our Property Quickstart Guide. This guide walks you through the process of integrating and using the Parcl API to efficiently retrieve property-level data.
The Parcl Labs Cookbook provides real-world property data code examples and use cases you can adapt for your specific needs.
How Credits Work for Property Data
Parcl Labs uses a simple credit-based consumption model: 1 credit = 1 property returned.
Learn more in the Credits Guide.
Property-Level Roadmap
The current version of the property-level API represents a subset of our unit-level data in terms of fields and historical coverage. We will work intentionally to expand these features over time.
Keep an eye out for these upcoming enhancements:
- Extended historical data
- Additional property and event fields
- Ability to search units by additional operators (i.e., inventory search)
Our team is focused on creating the best possible API developer and analytics experience for property data. If you have questions, feedback, or ideas, please post on our community forum or email us at [email protected].