Real-time unit-level data integrating property attributes with sales, listing, and rental events in a single, clean response
NOTE
Property-level data is a premium feature available only to starter or enterprise tier customers. To access it, upgrade your account on your API dashboard.
This API represents the first-ever housing API experience that lets you analyze all housing events across the property lifecycle - sales, listings, and rentals - at the unit level.
We are focused on creating the best API experience for accessing this data at scale. If you have questions, suggestions, or feedback, please post on our forum or email us at [email protected].
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 → Listed for Sale, Listing Removed, Other, Pending Sale, Price Change, Sold, Relisted ✅ 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: 📍 Location Details → Address, Unit, City, State, ZIP5, Latitude, Longitude 🏠 Property Attributes → Property Type, Bedrooms, Bathrooms, Square Footage, Year Built |
| Refresh Frequency | ✅ Daily |
| History | January 2010-Current |
Available endpoints
Gets a list of properties based on user-defined search parameters. Each property in the response includes a unique parcl_property_id, location detail, 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 Property Search when you need to find all properties that match specific criteria related to market, ownership, or property characteristics, returning a list of properties with their parcl_property_ids and key attributes.
Example Queries:
- Get all units with 3BR in zip code 12345
- Get all units currently owned by Invitation Homes in the Atlanta MSA that were built after 2020
- Get all new construction-related properties in Austin
Example Response:
Example JSON for a property returned by Property Search endpoint
Search for a specific address and retrieve the corresponding parcl_property_id for the property. 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, specifically Property Event History.
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
Gets unit-level properties and their housing event history, including sales, listings, and rentals. The response includes detailed property information and historical event data for each specified property. A maximum of 1000 parcl_property_ids can be requested in a single POST request.
Example Queries:
- Analyze current listings in Tampa to understand price cutting activity, using listing and price cut events to aggregate and understand trends.
- Compare performance of Home Partners portfolio acquired pre and post 2022, using property data to assess metrics like vacancy rates, rental rates, and yield across different acquisition periods.
Example JSON for events returned by Property Event History endpoint
Prerequisites
To use the Parcl Labs property-level API, you need:
- An API key (sign up or login here)
- Starter tier access (learn more here and upgrade via your API dashboard)
The property-level APIs are a premium offering available only to starter and enterprise tier customers.
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 Quickstart guide outlines a two-step workflow: First, you'll learn how to use the Property Market Search endpoint to find and list properties based on specific criteria. Then, it shows you how to use the Property Events endpoint to retrieve detailed historical event data for the properties you've identified. This approach allows you to quickly search for relevant properties and then access their event histories across sales, listing, and rental events.
How credits work for unit level data
Parcl Labs uses a credit-based consumption model for its API, rather than an API call-based model. If you're not familiar with our credit system, please read our credits overview guide.
It's important to understand:
- For Property Search (GET), each property returned = 1 credit.
- For Search Address (POST), each address searched, successfully matched, and returned = 1 credit.
- For Property Event History (POST), each event = 1 credit. Total credits used = Number of properties requested × Number of events per property
We've introduced new features to help with efficient credit management at the unit level:
- The new Property Search endpoint now includes flags to indicate whether you can expect sales, listings, and/or rental events in the currently available history (2010 - present).
- It also provides the number of events for each property (2010 - present)
These additions allow you to proactively estimate your credit consumption before pulling data.
Example:
- If you search for properties and receive 100 unique property results: 100 credits
- If you then request event history for these 100 properties, and each has an average of 5 events: Property Event History: 100 properties × 5 events = 500 credits
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)
- Capability to search units by address
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].