100 free credits. No credit card required.Start building
Logo
Homes.com logoHomes.com API

Get Homes.com listing data with one API

Read one Homes.com home by its link, for sale or for rent, with its exact facts, coordinates and photos, as structured JSON with one SocialCrawl API key. Reads are priced in credits.

Homes.com logo
/v1/homes

1 active endpoint. Home detail.

  • GET /v1/homes/property

What Homes.com endpoints does SocialCrawl ship?

One read endpoint for public Homes.com data: read one home by its link, for sale or for rent.

Home detail

1 credit
/v1/homes/property

One home by its Homes.com link: price, status, beds, the exact bath count, square feet, lot size, year built, coordinates, the brokerage, the description and the photo gallery. Homes.com sends no price or tax history here. Standard tier (1 credit).

url

Homes.com API1 endpoint supported
View docs
Listings

Returns one Homes.com home by its link: price, status, beds, the exact bath count, size, lot, year built, coordinates, the brokerage, the description and the photo gallery.

Use it with a Homes.com home link when you need one home's exact facts, description and photos.

1 credit

GET/v1/homes/property?url=https%3A%2F%2Fwww.homes.com%2Fproperty%2F4508-duval-rd-austin-tx-unit-604%2F4wgt29y2rsx2g%2F

url · A Homes.com home link under /property/, for example https://www.homes.com/property/4508-duval-rd-austin-tx-unit-604/4wgt29y2rsx2g/.

$ curl https://www.socialcrawl.dev/v1/homes/property?url=https%3A%2F%2Fwww.homes.com%2Fproperty%2F4508-duval-rd-austin-tx-unit-604%2F4wgt29y2rsx2g%2F \
    -H "x-api-key: sc_YOUR_API_KEY"
idle
// Running this live needs your own API key. Hit "Try it" to see an example response

How the Homes.com API works

Homes.com is a normal SocialCrawl data surface. You call GET /v1/homes/… with an API key, spend credits on live misses, and get a single JSON envelope back.

Authenticate every call

Send your key in the x-api-key header. No Homes.com account or partner access is needed for public reads. The same key works across SocialCrawl platforms.

GET with query params

Property takes url, a home's Homes.com link. Formats are validated before any charge.

Pay in credits, not seats

The Homes.com route costs 1 credit. Cache hits cost 0.

Read one JSON envelope

Every response is the same shape: success, data, credits_used, credits_remaining, request_id, cached. Lists also carry pagination when the route pages.

The usual integration chain

Most products read the homes they follow by their Homes.com link, often on a schedule.

01Read a home for sale
GET /v1/homes/property?url=…

Place with the listing facts, the description and photos

Pass the home's Homes.com link as url.

02Read a home for rent
GET /v1/homes/property?url=https%3A%2F%2Fwww.homes.com%2Fproperty%2F…

Place with status for_rent

On a rental the price is the monthly rent.

request
GET /v1/homes/property?url=https%3A%2F%2Fwww.homes.com%2Fproperty%2F4508-duval-rd-austin-tx-unit-604%2F4wgt29y2rsx2g%2F
Host: www.socialcrawl.dev
x-api-key: sc_your_api_key_here
response envelope
{
  "success": true,
  "data": {
    "place": {
      "id": "4wgt29y2rsx2g",
      "name": "4508 Duval Rd Unit 604",
      "ext": {
        "listing": {
          "price": 334500,
          "currency": "USD",
          "status": "for_sale",
          "beds": 2,
          "baths": 2.5,
          "sqft": 1383,
          "broker": "Compass RE Texas, LLC"
        }
      }
    }
  },
  "credits_used": 1,
  "credits_remaining": 9999,
  "request_id": "req_…",
  "cached": false
}

What lands in data

Field names match the rest of SocialCrawl where archetypes align. Parse once, reuse across platforms.

Placeproperty

the listing facts with the exact baths, lot_sqft and year_built, plus coordinates, the description and image_urls[]; no price or tax history

Listing statusproperty

status for_sale or for_rent; on a rental, price is the monthly rent

Inside the gateway

Same request lifecycle as every other /v1 platform endpoint. Homes.com is not a sidecar.

  1. 01

    Edge receives the call

    Next.js catch-all routes into the Hono social API. We mint a request_id, authenticate the key, then enforce rate limit (600/min) and concurrency (50 in flight per key).

  2. 02

    Validate, then debit

    Registry lookup finds the homes route. Required params and format checks run first. Invalid input returns 400 with no charge. Valid calls debit the tier cost atomically before the read starts.

  3. 03

    Cache or fetch

    A deterministic cache key is built from platform + resource + params. Hit: return immediately, credits_used = 0. Miss: the public page is read live, with retries on 5xx or network errors and a circuit breaker if the source is unhealthy.

  4. 04

    Normalize and return

    Homes.com data is mapped to the Place archetype with the listing facts in place.ext.listing, validated, then wrapped in the success envelope and logged for billing audit.

Billing rules that matter in production

  • property: 1 credit
  • Cache hit: 0 credits
  • Empty / hard fail: auto-refund
  • Bad params: 400, never charged
  • No credits: 402, never charged
  • No price history on this source
  • Money in US dollars, areas in square feet
  • No agent contact, tour or offer tools
  • landings.platformBrief.platforms.homes.api.billingRules.8

How SocialCrawl gets Homes.com data

Homes.com is public read data. We normalize it into the SocialCrawl schema so your code does not learn a second vendor SDK.

What Homes.com is for this API

Public home pages for homes for sale and for rent in the United States, with price or monthly rent, beds, baths, size, lot size, year built and the listing brokerage.

How SocialCrawl reaches it

Public pages are read on request and normalized server-side. You never run a Homes.com login or partner integration.

What leaves our edge

Place for one home. The listing facts sit in place.ext.listing, the same shape Zillow, Redfin and Realtor.com homes use.

What we do not ship live

No price history, agent contact, tour requests, offers or saved searches.

field map sketch
Homes.com home→ place.*Homes.com property id, street line, full address, and coordinates on the home detail
listing facts→ place.ext.listingprice or monthly rent, status, beds, baths (home detail), square feet, lot size, brokerage

What this API is used for

The jobs this API is most often used for.

1active Homes.com endpoints in the registry
1credit per call on the Homes.com route

Home detail by link, for sale and for rent

Callers read the homes they follow by their Homes.com link, often on a schedule. For-sale and rental homes read by link, with the exact bath count, from one key in the shared Place schema Zillow, Redfin and Realtor.com homes use.

Live misses read the public page on request. Repeat calls hit cache and cost 0 credits.

Use case examples

Common ways teams put this data to work, and the stack each one tends to run.

Price tracking by home

Node, scheduled jobs

property on the same home links on a schedule to see which homes changed price or status.

Rental listings

Python, notebooks

property on rental home links to record asking rents, beds and baths.

Cross-site listing coverage

Python, warehouse loads

read the same home on Homes.com, Realtor.com, Zillow and Redfin and join on address to compare what each site shows.

How to call the Homes.com API

The Homes.com route is 1 credit. Cache hits are free.

curl "https://www.socialcrawl.dev/v1/homes/property?url=https%3A%2F%2Fwww.homes.com%2Fproperty%2F4508-duval-rd-austin-tx-unit-604%2F4wgt29y2rsx2g%2F" \n  -H "x-api-key: sc_your_api_key_here"
Homes.com logoHomes.com on SocialCrawl

Same key as the rest of the catalog

Endpoints

What data does the Homes.com API return?

Every endpoint returns structured JSON in a unified envelope. Computed fields such as engagement rate and content category are included only where the endpoint supports them and the required source inputs are present.

FAQ

Have a question? We got answers

Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.

Contact us
What does the SocialCrawl Homes.com API cover?
It covers 1 endpoints: Property. It reads one Homes.com home by its link, for sale or for rent, in the same unified JSON as the other 94 platforms.
Can I get Homes.com rental listings?
Yes. Pass the link of a home for rent on Homes.com. The record comes back with status for_rent and the monthly rent as the price.
Does the Homes.com API return price history?
No. Homes.com home records carry the current price only, so place.ext.listing.price_history is null. Zillow and Redfin homes return their price and tax history on SocialCrawl.
Which facts does a Homes.com home record carry?
GET /v1/homes/property returns the price, beds, the exact bath count, size, lot size, year built, the coordinates and the brokerage. Agents' names and phone numbers are not published.
How much does the Homes.com API cost?
The Homes.com route costs 1 credit a call and cache hits are free. A new account gets 100 free credits with no card.
Is scraping Homes.com data legal?
SocialCrawl returns publicly available Homes.com data and does not access private or login-gated content. Whether scraping fits your project depends on your use case and jurisdiction. You are responsible for complying with Homes.com's terms of service and applicable data-protection laws such as GDPR and CCPA. This is general information, not legal advice.
Homes.com scraping API vs the official Homes.com API: what's the difference?
With SocialCrawl there is no app review or approval queue. Sign up and call Homes.com endpoints immediately with a single x-api-key. Responses share one unified schema with every other SocialCrawl platform, and credit-based pricing replaces per-platform quotas. Official APIs are still the right choice for posting and other write actions: SocialCrawl is read-only data.

Ask AI about SocialCrawl

Read the Homes.com API reference in the docs

🤖 AI agent or LLM? Read this page as markdown