Our latest API release added a more robust query engine and new property and listing search capabilities, introduced automatic subject property attribute lookup for AVM endpoints, and added many other improvements and features.

Check out the highlights below:

General Improvements

• We've added the stateFips and countyFips fields to all API responses that return a property address, representing the FIPS codes assigned to each state and county
• We've improved our property address parser and made it more tolerant to malformed addresses, city and zip code mismatches, and other formatting inconsistencies
• We've improved the consistency and format of county and county-equivalent names throughout our database
• All API endpoints now support a new suppressLogging boolean query parameter. If provided with a "true" value, it will prevent internal logging of your API queries and query parameters, to address data security or compliance requirements
• We've improved the speed and performance of many API endpoints, specifically those that support complex queries and pagination

Property Records (/properties)

• The propertyType query parameter now supports multiple values, separated by the pipe character | (ex. "Single Family|Condo|Townhouse")
• The bedrooms and bathrooms query parameters now support multiple values, separated by the pipe character | (ex. "1|3"). They also now support a min-max value range, separated by the colon character : (ex. "1:3")
• We've added 3 additional query parameters that support multiple values (separated by the pipe character |) and min-max value ranges (separated by the colon character :):
  • squareFootage: this query parameter can be used to search and filter properties by their indoor living area size
  • lotSize: this query parameter can be used to search and filter properties by their lot size
  • yearBuilt: this query parameter can be used to search and filter properties by the year they were built

• The saleDateRange query parameter now accepts a min-max value range, separated by the colon character : (ex. "180:270"). The existing behavior of this parameter is unchanged - if a single value is provided, it is treated as the maximum range value
• It is now possible to retrieve the total number of property records matching a specific query by using the new includeTotalCount boolean query parameter, with a "true" value. The total record count will be returned in the X-Total-Count header of the response. Please note that this may significantly increase the response time of this endpoint, and it is recommended to use this sparingly
• Responses from this endpoint will now return the X-Limit and X-Offset headers, which represent the values of the limit and offset query parameters that were used when performing bulk search queries
• We've improved the consistency and format of property features and characteristics returned in the features response field

Random Property Records (/properties/random)

• Responses from this endpoint will now return the X-Limit header, which represents the value of the limit query parameter that was used when performing the search query
• We've significantly improved the speed and performance of this endpoint to bring it up to par with our other API endpoints

Property Valuation (/avm/value, /avm/rent/long-term)

• We've added a new lookupSubjectAttributes boolean query parameter to our AVM endpoints. When provided with a "true" value, it will enable automatic lookup of subject property attributes (property type, bedrooms, bathrooms, square footage) before calculating and returning the estimated property value or rent:
  • This query parameter defaults to "true", meaning our API will now automatically look up subject property attributes for you. This should increase the AVM accuracy for the majority of use cases, so we recommend leaving this parameter enabled
  • You can still provide your own subject property attributes via the propertyType, bedrooms, bathrooms, and squareFootage query parameters. If provided, these values will override any subject property attributes that are looked up automatically
  • In rare cases, you may wish to turn off this behavior by providing the lookupSubjectAttributes query parameter with a "false" value. This will preserve the legacy behavior of our AVM endpoints before this change

• Responses from the AVM endpoints will now return a new subjectProperty field, which will include the address, coordinates, attributes, and other information pertaining to the subject property location
• The top-level latitude and longitude fields are now considered deprecated and will be removed in a future API update. We encourage you to update your code to use the newsubjectProperty.latitude and subjectProperty.longitude fields instead
• Comparable property records will now return the listing status field. See explanation of listing statuses for possible values

Property Listings (/listings/sale, /listings/rental/long-term)

• The propertyType query parameter now supports multiple values, separated by the pipe character | (ex. "Single Family|Condo|Townhouse")
• The bedrooms and bathrooms query parameters now support multiple values, separated by the pipe character | (ex. "1|3"). They also now support a min-max value range, separated by the colon character : (ex. "1:3")
• We've added 4 additional query parameters that support multiple values (separated by the pipe character |) and min-max value ranges (separated by the colon character :):
  • price: this query parameter can be used to search and filter listings by their listed price or rent
  • squareFootage: this query parameter can be used to search and filter listings by their indoor living area size
  • lotSize: this query parameter can be used to search and filter listings by their lot size
  • yearBuilt: this query parameter can be used to search and filter listings by the year they were built

• The daysOld query parameter now accepts a min-max value range, separated by the colon character : (ex. "30:60"). The existing behavior of this parameter is unchanged - if a single value is provided, it is treated as the maximum range value
• It is now possible to retrieve the total number of listing records matching a specific query by using the new includeTotalCount boolean query parameter, with a "true" value. The total record count will be returned in the X-Total-Count header of the response. Please note that this may significantly increase the response times of these endpoints, and it is recommended to use this sparingly
• Responses from these endpoints will now return the X-Limit and X-Offset headers, which represent the values of the limit and offset query parameters that were used when performing bulk search queries
• We've improved rental listing coverage for large apartment complexes and multi-family buildings in many markets

Integrations & Support Resources

• All API guides and endpoint reference pages now include an Ask AI dropdown at the top, which you can use to quickly share our API documentation with AI assistants and agents
• We now publish a special LLMs.txt markdown file designed to help AI assistants and agents better understand and work with our documentation. See this file here
• We have created a RentCast API MCP server, available at https://developers.rentcast.io/mcp, to assist with connecting our API and data directly to AI tools, code editors, applications, and agents. View this guide for instructions on how to connect to our MCP server

Our API documentation has been updated to reflect the above changes, and you can view it at any time to review our data sets and API endpoints in more detail.

If you have any questions about this update, or have additional feature requests or suggestions, contact us by launching the live chat at the bottom right of this website, or by sending an email to [email protected].

👍

Getting Started

To get started using our property data API, create a RentCast account to access your API dashboard and generate your first API key. Read this guide for an in-depth walkthrough.

This API release added sale market statistics and new aggregate market data points, MLS numbers and listing agent information for property listings, HOA fee amounts, and listing and property transaction history.

Check out the highlights below:

Property Records (/properties)

• We've added a saleDateRange query parameter, which accepts a numeric value in days. You can use this parameter to search for properties that were sold within the specified date range
• Property records will now include an hoa field if they are part of a homeowner's association. This field will contain a fee property, indicating the monthly HOA fee or assessment amount
• Property records will now include an owner.type field, with possible values of "Individual" or "Organization", indicating the type of entity that owns the property
• Property records will now include a history field, which contains the sale transaction history of that property

Property Valuation (/avm/value, /avm/rent/long-term)

• We've added several additional fields to the comparable property records returned by the AVM endpoints:
  • listingType: the type of the comparable property listing, with possible values of "Standard", "New Construction", "Foreclosure" or "Short Sale"
  • removedDate: the date the comparable property listing was removed from the market
  • daysOnMarket: the number of days the comparable property listing was active on the market before being removed

Property Listings (/listings/sale, /listings/rental/long-term)

• We've added several additional fields to the property listing records returned by the listing endpoints:
  • hoa: for listings that are part of a homeowner's association, this field will contain a fee property, indicating the monthly HOA fee or assessment amount
  • listingType: the type of the listing, with possible values of "Standard", "New Construction", "Foreclosure" or "Short Sale"
  • mlsName: the MLS name of the listing, if listed on the Multiple Listing Service (MLS)
  • mlsNumber: the MLS number or unique identifier of the listing, if listed on the Multiple Listing Service (MLS)
  • listingAgent: includes the name and contact information of the listing agent of the property
  • listingOffice: includes the name and contact information of the listing office or brokerage of the property
  • builder: for new construction listings, includes the name and contact information of the builder of the property, as well as the name of the new development community or subdivision

• Listing records will now include a history field, which contains the sale or rental listing history of that property

Market Statistics (/markets)

• We've added aggregate sale market statistics and property sale price trends for most zip codes in the US as part of the response from this endpoint:
  • Sale market statistics will be returned in the top-level saleData field
  • Historical sale market statistics are available from January 2024
  • You can control the type of market statistics data returned by this endpoint with the new dataType query parameter, with supported values of "Sale", "Rental" or "All"

• Both sale and rental market statistics will now include several additional fields and metrics, beginning in August 2024:
  • Median price or rent
  • Average/median/min/max price or rent per square foot
  • Average/median/min/max square footage of listed properties
  • Average/median/min/max days on the market of listed properties
  • The number of new property listings added in a given month

• Both sale and rental market statistics will now include data and averages broken down by property type, in addition to the existing breakdown by bedroom count:
  • Data broken down by property type will be returned in the dataByPropertyType field
  • Historical data broken down by property type is available from August 2024

Integrations & Support Resources

• We've released a public PostMan workspace and an API endpoints collection that includes a full reference of our available endpoints, their supported query parameters and example responses
• We've added a public GitHub workspace that includes several additional resources for integrating with our API, including our OpenAPI specification and our public PostMan collection export

Our API documentation has been updated to reflect the above changes and you can view it at any time to review our data sets and API endpoints in more detail.

If you have any questions about this update, or have additional feature requests or suggestions, contact us by launching the live chat at the bottom right of this website, or by sending an email to [email protected].

👍

Getting Started

To get started using our property data API, create a RentCast account to access your API dashboard and generate your first API key. Read this guide for an in-depth walkthrough.

This month we've released the RentCast Zapier integration, improved the consistency of historical market data, and made it easier to view API request metrics for specific API keys.

Check out the highlights below:

RentCast Zapier Integration

The RentCast Zapier integration is now live and available to anyone with a Zapier account.

In case you're not familiar with Zapier, it is a popular automation platform that allows you to connect over 6,000 apps and services without writing any code or custom scripts.

With our new Zapier integration, you can quickly connect any of the property and rental data available through our API to thousands of apps, CRM systems, email clients, spreadsheets, and other apps to create custom workflows and automations.

API Dashboard Improvements

• You can now filter your API request metrics by a specific API key, and view API requests, errors and latencies for each of your apps or integrations from your API dashboard

Property Valuation (/avm/value, /avm/rent/long-term)

• The AVM endpoints will now return 15 comparable properties by default (instead of 10) when the compCount query parameter is not provided
• We've increased the accuracy of our value and rent estimates for properties with a studio layout (when the bedrooms query parameter is set to 0)

Property Listings (/listings/sale, /listings/rental/long-term)

• We've improved the accuracy of the property address parser in our listing endpoints, so you should see fewer cases when an address you provided could not be located

Market Statistics (/markets)

• We've improved the consistency and accuracy of historical rental market data by removing outlier spikes and inconsistent historical data points
• We've added the lastUpdatedDate field to the market statistics endpoint responses that indicates the date data was last updated

Our API documentation has been updated to reflect the above changes and you can view it at any time to review our data sets and API endpoints in more detail.

If you have any questions about this update, or have additional feature requests or suggestions, contact us by launching the live chat at the bottom right of this website, or by sending an email to [email protected].

👍

Getting Started

To get started using our property data API, create a RentCast account to access your API dashboard and generate your first API key. Read this guide for an in-depth walkthrough.

This API release added two new endpoints for retrieving individual property listings, improved our property data coverage, and increased AVM estimate accuracy.

Check out the highlights below:

New Endpoints - Property Listings by Id (/listings/sale/{id}, /listings/rental/long-term/{id})

• We have added two new API endpoints, which allow you to retrieve specific sale or rental listings by their internal property id
• Use the /listings/sale/{id} endpoint to retrieve individual sale listings
• Use the /listings/rental/long-term/{id}endpoint to retrieve individual rental listings
• Property ids can be obtained via the /properties, /avm or /listings endpoints, or cached in your application from prior requests

General Improvements

• We've improved the accuracy of our property address parser, so you should see fewer cases when an address you provided could not be located
• We've improved the speed and performance of many endpoints, especially those that perform geospatial queries

Property Records (/properties)

• We've improved our property data coverage in many counties, so you should see an increased property data availability across the board

Property Valuation (/avm/value, /avm/rent/long-term)

• We've increased the maximum value of the compCount parameter to 25, so you can now retrieve up to 25 comparable properties in each request
• We've increased the accuracy of our value and rent estimates by improving our comparable correlation algorithm

Our API documentation has been updated to reflect the above changes and you can view it at any time to review the newly supported endpoints in more detail.

If you have any questions about this update, or have additional feature requests or suggestions, contact us by launching the live chat at the bottom right of this website, or by sending an email to [email protected].

👍

Getting Started

To get started using our property data API, create a RentCast account to access your API dashboard and generate your first API key. Read this guide for an in-depth walkthrough.

Our latest API release added many new query parameters to help you search for property records and listings more efficiently, improved API response times, and made several other improvements.

Check out the highlights below:

General Improvements

• Added support for theManufactured and Land property types across all endpoints. You can use these new types when using the propertyType query parameter, and you will also see them as part of the returned property and listing records
• Improved the performance of all endpoints across the board, so you should see decreased latencies when performing your requests

Property Records (/properties)

• Added a zipCode query parameter, which you can use to search for properties in a specific zip code
• Added a propertyType query parameter, which you can use to search for properties matching a specific property type
• Increased the maximum value of the limit query parameter to 500, so you can now retrieve up to 500 property records in a single request

Random Property Records (/properties/random)

• Increased the maximum value of the limit query parameter to 500, so you can now retrieve up to 500 random property records in a single request

Property Valuation (/avm/value, /avm/rent/long-term)

• Added a maxRadius query parameter, which you can use to control the maximum distance (in miles) of the comparable properties used in the valuation estimate calculations
• Reduced the minimum value of the daysOld query parameter from 15 to 1 day
• The AVM endpoints will now return 10 comparable properties by default (instead of 5) when the compCount query parameter is not provided

Property Listings (/listings/sale, /listings/rental/long-term)

• Added a zipCode query parameter, which you can use to search for listings in a specific zip code
• Added a propertyType query parameter, which you can use to search for listings matching a specific property type
• Added a status query parameter, which you can use to search for only active or inactive listings
• Added a daysOld query parameter, which you can use to filter listings that were posted within the provided number of days
• Increased the maximum value of the limit query parameter to 500, so you can now retrieve up to 500 property listings in a single request

Our API documentation has been updated to reflect the above changes and you can view it at any time to review the newly supported query parameters in more detail.

If you have any questions about this update, or have additional feature requests or suggestions, contact us by launching the live chat at the bottom right of this website, or by sending an email to [email protected].

👍

Getting Started

To get started using our property data API, create a RentCast account to access your API dashboard and generate your first API key. Read this guide for an in-depth walkthrough.

Welcome to the first release of the RentCast property data API! 🚀

This is the initial release of our API, which includes the following endpoints:

Property Data

Retrieve data for over 140 million properties in the United States, covering most residential and commercial properties in the country:

• /properties
• /properties/random
• /properties/{id}

Property Valuation

Retrieve real-time property value and rent estimates for most residential and commercial properties in the US:

• /avm/value
• /avm/rent/long-term

Property Listings

Search for and retrieve active and historical sale and rental listings nationwide in the United States:

• /listings/sale
• /listings/rental/long-term

Market Data

Retrieve aggregate rental data, statistics, and historical trends for most zip codes in the United States:

• /markets

👍

Getting Started

To get started using our property data API, create a RentCast account to access your API dashboard and generate your first API key. Read this guide for an in-depth walkthrough.