Question 1

How many properties do you have data on?

Accepted Answer

RealEstateAPI covers 160+ million properties nationwide, providing comprehensive coverage across all U.S. states with property ownership records, tax data, and listing information where available. This includes residential, commercial, and industrial properties with detailed information on ownership, valuation, and transaction history.

Question 2

How fresh is the property data?

Accepted Answer

Property data is updated daily with new sales, ownership changes, and MLS listings. Public record updates vary by county (weekly to monthly), while MLS data refreshes in real-time from participating boards. We maintain partnerships with over 800 counties nationwide to ensure the most current information available.

Question 3

What skip tracing data is available for property owners?

Accepted Answer

Skip tracing includes phone numbers, email addresses, current and previous addresses, relatives, associates, and social media profiles. Coverage varies by property but typically provides multiple contact methods per owner. Our skip tracing service aggregates data from hundreds of public and private sources to ensure comprehensive contact information. Learn more: https://developer.realestateapi.com/reference/skiptrace-api

Question 4

Does the API cover commercial properties such as office buildings and retail centers?

Accepted Answer

The API primarily covers residential properties with comprehensive nationwide coverage. Commercial properties (office, retail, industrial, multi-family) are included where available, but data completeness varies significantly by county and property type. For commercial-focused applications, contact us to discuss coverage for your target markets. Or click below to view a full list of available property use codes Learn more: https://developer.realestateapi.com/reference/commercial-cre-search

Question 5

How do I search for properties with assumable mortgages?

Accepted Answer

Yes. In the Property Search API you can filter for assumable loans using the top-level `assumable` boolean filter.

Question 6

How do I search for properties with specific mortgage characteristics?

Accepted Answer

Use the Property Search API with mortgage filter parameters to find properties by mortgage balance, private lender status, or free & clear status. Mortgage data like loan type and interest rate is available in the Property Detail response.

Question 7

Can I get property foreclosure filing dates and auction information?

Accepted Answer

Yes, foreclosure data includes filing dates, auction dates, case numbers, default amounts, trustee information, and auction addresses. Use foreclosure: true or pre_foreclosure: true in searches. We track properties through every stage of the foreclosure process from initial filing to auction completion.

Question 8

What's the difference between an Automated Valuation Model (AVM) and a Broker Price Opinion (BPO)?

Accepted Answer

AVM (Automated Valuation Model) uses statistical modeling and comparable sales for instant estimates. BPO (Broker Price Opinion) requires human analysis but provides more nuanced market insights. Our Lender Grade AVM provides confidence scores and valuation ranges to give more nuance than a single value figure can convey. AVMs are faster and more cost-effective, while BPOs offer deeper market analysis for complex properties.

Question 9

How accurate are Automated Valuation Models (AVMs) compared to human appraisals?

Accepted Answer

Our Lender Grade AVM typically achieves 85-90% accuracy within 10% of appraisal value, with confidence scores indicating reliability. Multi-model approach and recent sales data improve precision over single-model systems. Accuracy varies by market conditions, property type, and availability of comparable sales data.

Question 10

How far back does the property ownership history data go?

Accepted Answer

Property historical data ranges from state to state. But 10 to 20 years of transaction history is common. Some counties provide records dating back 30+ years, while others may have limited historical data due to digitization timelines.

Question 11

How does your API solution compare to working with a flat file?

Accepted Answer

Flat files can deliver timely data, but only if you manage a cadence of regular file deliveries and maintain pipelines to push those updates into your systems. An API eliminates that overhead by delivering always-current data in real time. Our API also supports complex filtering, advanced search functions such as radius queries, and automatic refreshes. Typical response times are under 100ms, which flat files cannot match. APIs also provide better error handling, authentication, and usage tracking capabilities.

Question 12

How many API calls does it take to get a complete property analysis with comps and owner data?

Accepted Answer

As few as 1 API call using Property Detail with comps: true. For more control, use 2-3 separate calls for property details, comps, and valuation. A complete property analysis requires 1-3 API calls depending on your workflow:

**Most efficient (1 call):** Property Detail with `comps: true` → returns property data, owner info, AND comparable sales in a single response

**Modular approach (2-3 calls):**
- Property Detail → property characteristics and owner data
- Property Comps → comparable sales with customizable filters (radius, date range, exact match criteria)
- Property AVM (optional) → dedicated valuation with confidence scores

Question 13

Can I call the RealEstateAPI directly from my React frontend, or do I need a backend?

Accepted Answer

You can hit the API from the browser, but best practice is to call it from your backend so you don't expose your API key and so you can control rate limits and usage. Yes — technically the API is just HTTPS+JSON, so the browser can call it. But the recommended pattern is:

Your React app → hits your backend (or edge function)
Your backend → calls RealEstateAPI
Your backend → returns only the fields your UI needs

**Why we recommend this:**
- Keeps your API key/secret out of the browser
- Lets you enforce per-user limits (otherwise one user can blow through your credits)
- Lets you normalize / map the RealEstateAPI payload into your internal shape
- Lets you log and meter usage per tenant/customer

Question 14

How do I validate addresses before running property searches?

Accepted Answer

Use the Address Verification API to validate and standardize addresses before searching. It returns a corrected, geocoded address that ensures accurate property matches.

**Recommended workflow:**
1. AutoComplete → guide user input with real-time suggestions (free for subscribers)
2. Address Verification → validate and standardize the selected address
3. Property Search/Detail → use the verified address for accurate results

**Rate Limits:**
- Address Verification: Max 100 addresses per request, 10 req/sec per API key
- AutoComplete: Unlimited free use for monthly subscribers

Question 15

What are the API rate limits and throttling rules?

Accepted Answer

Rate limits vary by endpoint and are measured in credits per 24-hour window. Property Search allows 1,000,000 credits per day (excluding 'count' or 'ids_only' calls), while Property Detail/Bulk endpoints allow 500,000 credits per day. Address Verification has specific limits of 10 requests/second by API key and 3 requests/second per user ID, with up to 100 addresses per request. Contact support for higher limits if needed.

Question 16

Do you offer bulk endpoints to accommodate processing for large property lists?

Accepted Answer

Yes, the Property Detail Bulk endpoint processes up to 1,000 property IDs in a single request. Use ids_only: true in Property Search to retrieve IDs, then batch them through the bulk endpoint. Learn more: https://developer.realestateapi.com/reference/property-detail-bulk-api

Question 17

What code samples, or client libraries are available?

Accepted Answer

You can access our Postman collections here: https://www.postman.com/realestateapis. We also provide code samples in Python, Node.js, PHP, and other popular languages in our developer documentation.

Question 18

What pricing plans do you offer?

Accepted Answer

We have three plan tiers: Starter ($599/mo), Growth ($1200/mo) and Pro ($2500/mo). As you ascend in the plans you get access to more endpoints--and more property records are included. Each plan includes different credit allocations and feature access to match your business needs.

Question 19

Can I change my plan at any time?

Accepted Answer

Yes, upgrade or downgrade anytime. Changes take effect at the top of the following month. Monitor usage through the API dashboard to optimize your plan selection. Prorated billing applies for mid-cycle upgrades.

Question 20

What payment methods do you accept?

Accepted Answer

Credit cards (Visa, MasterCard, American Express, Discover) and ACH bank transfer. Detailed invoicing and usage tracking available in our user console. Enterprise accounts can also arrange wire transfer payments.

Question 21

What's included in the free trial?

Accepted Answer

It is a 2-week trial with full API access and credit allocation for testing all endpoints.

Question 22

What happens if I exceed my monthly credit limit?

Accepted Answer

Each unit of overage is billed at the same unit price for your subscription plan.

Question 23

Do you offer pay as you go plans?

Accepted Answer

Yes, we now offer pay as you go plans. They are month to month access. For a small premium you can have maximum flexibility. Annual subscriptions offer the most favorable pricing. Learn more: https://www.realestateapi.com/pricing#payg

Question 24

Do you offer enterprise pricing or volume discounts?

Accepted Answer

Yes, Enterprise accounts get access to volume discounts as well as custom development and priority support. If you're interested in our highest tier of service, contact sales by clicking below. Learn more: https://www.realestateapi.com/booking

Question 25

Can I generate neighborhood or market-level analytics using the API?

Accepted Answer

Yes. Use Property Search with geographic filters (city, county, ZIP, radius, or polygon) to retrieve properties, then aggregate the data for neighborhood or market-level analytics. The Property Search API returns property-level data that you can aggregate into neighborhood or market analytics. Use geographic filters to define your area, then calculate metrics from the results.

Question 26

Can I integrate the API with my CRM or marketing automation tools?

Accepted Answer

Yes, the API supports integration with popular CRM and marketing platforms including Salesforce, Hubspot and GoHighLevel.

Question 27

How do I use the API for underwriting or loan qualification workflows?

Accepted Answer

Use Property Detail for property characteristics and ownership, Property AVM for valuation, and Property Comps for market validation. Combine this data with your underwriting criteria to automate qualification workflows. The API provides key data points for underwriting and loan qualification workflows. Retrieve property valuation, ownership, lien information, and market comparables, then apply your underwriting criteria programmatically.

**Typical underwriting workflow:**
1. Address Verification → validate and standardize the subject property address
2. Property Detail → get property characteristics, tax assessment, existing mortgages/liens, owner information
3. Property AVM → automated valuation with confidence scores and value ranges
4. Property Comps → validate AVM with recent comparable sales

Question 28

What advanced search and filtering options are available?

Accepted Answer

Our API offers nearly 100 different search parameters. They can be combined into any permutation to produce compound queries. Advanced filtering includes things like geographic boundaries, property characteristics, and market conditions. Learn more: https://developer.realestateapi.com/reference/property-search-field-guide

Frequently Asked Questions

Data Coverage & Quality