Homes.co.nz Property Search Scraper
Pricing
Pay per event
Homes.co.nz Property Search Scraper
Extract Homes.co.nz address, suburb, street, and property search candidates for NZ real estate research, geocoding, and lead enrichment.
Pricing
Pay per event
Rating
0.0
(0)
Developer
Stas Persiianenko
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
Extract public Homes.co.nz property search, address lookup, suburb, street, and city suggestions for New Zealand real estate workflows.
The actor queries public Homes.co.nz gateway endpoints and returns clean dataset rows with titles, result types, address components, coordinates, IDs, source URLs, and timestamps.
What does Homes.co.nz Property Search Scraper do?
Homes.co.nz Property Search Scraper turns Homes.co.nz search terms into structured property discovery data.
Use it to search public address, street, suburb, and city candidates across New Zealand.
Typical terms include city names, suburbs, streets, and full addresses.
The actor is HTTP-first and does not require a browser, login, or account cookies.
Who is it for?
- π Real estate agencies building address and area prospecting lists.
- π Proptech teams enriching NZ address search workflows.
- π Market researchers monitoring property discovery coverage.
- π§ GIS and geocoding teams comparing candidate locations.
- πΌ Investors looking for repeatable suburb and street discovery exports.
- π€ Lead enrichment teams that need public Homes.co.nz search metadata.
Why use this scraper?
Manual Homes.co.nz search is useful for one-off checks.
This actor is useful when you need repeatable exports, multiple search terms, or an API-friendly workflow.
It returns consistent fields that are easier to merge into spreadsheets, CRMs, GIS tools, BI dashboards, and enrichment pipelines.
What data can you extract?
| Field | Description |
|---|---|
searchTerm | Input term used for the gateway query |
resultType | Normalized result type such as city, suburb, street, address, property, or listing |
title | Homes.co.nz result title |
score | Gateway relevance score when returned |
latitude / longitude | Result coordinates |
city, suburb, street | Address components |
streetNumber, unitIdentifier | Address detail when available |
suburbId, cityId | Homes.co.nz location IDs |
propertyId, listingId | Public IDs when the gateway returns them |
size | Area or result size value |
sourceUrl | Homes.co.nz search URL for traceability |
scrapedAt | ISO timestamp |
How much does it cost to scrape Homes.co.nz property search data?
This actor uses pay-per-event pricing.
You pay a small start fee and a per-result charge for saved dataset rows.
The input prefill is intentionally small enough for a cheap first run.
Use maxItems to control spend for broad multi-city jobs.
How to use Homes.co.nz Property Search Scraper
- Open the actor on Apify.
- Add one or more New Zealand search terms.
- Choose
typeaheadfor broad discovery oraddressfor stricter address matching. - Set
maxItems. - Run the actor.
- Export the dataset as JSON, CSV, Excel, XML, or via API.
Input example
{"searchTerms": ["auckland","queen street auckland","wellington","christchurch","hamilton"],"maxItems": 100,"searchMode": "typeahead","includeCentroid": false,"includeRawData": false}
Output example
{"searchTerm": "auckland","searchMode": "typeahead","resultTypeCode": 1,"resultType": "city","title": "Auckland","score": 72.81268,"latitude": -36.84985594022932,"longitude": 174.76370664609487,"city": "Auckland","suburb": null,"street": null,"streetNumber": 0,"suburbId": 0,"cityId": 8,"sourceUrl": "https://homes.co.nz/search/auckland","scrapedAt": "2026-07-07T00:00:00.000Z"}
Search term tips
Use broad city terms for coverage.
Use suburb terms for local market lists.
Use street names plus a city for address candidate discovery.
Use exact full addresses when you want stricter matching.
Use multiple terms when you need more than the gateway returns for one term.
Search modes
typeahead is best for broad public search discovery.
address is useful when you want address-focused candidates.
Both modes call public Homes.co.nz JSON endpoints.
Centroid enrichment
Set includeCentroid to true to request centroid data for area and street results.
Centroid fields can help mapping workflows by adding a central coordinate and size estimate.
If Homes.co.nz does not return centroid data for a row, the actor keeps the row and leaves centroid fields empty.
Raw data option
Set includeRawData to true when you want the original gateway object attached to every row.
This is useful for custom mapping, troubleshooting, or checking newly added upstream fields.
Leave it off for cleaner exports.
Integrations
- π§Ύ Export CSV rows into Google Sheets for lead review.
- πΊοΈ Load coordinates into GIS tools for suburb and street mapping.
- π§ Send JSON to enrichment pipelines that normalize address candidates.
- π Combine recurring runs with BI dashboards to monitor search coverage.
- π Use Apify webhooks to trigger downstream updates after each run.
API usage with Node.js
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: process.env.APIFY_TOKEN });const run = await client.actor('automation-lab/homes-co-nz-property-search-scraper').call({searchTerms: ['auckland', 'wellington'],maxItems: 100,searchMode: 'typeahead'});console.log(run.defaultDatasetId);
API usage with Python
from apify_client import ApifyClientclient = ApifyClient('YOUR_APIFY_TOKEN')run = client.actor('automation-lab/homes-co-nz-property-search-scraper').call(run_input={'searchTerms': ['auckland', 'wellington'],'maxItems': 100,'searchMode': 'typeahead',})print(run['defaultDatasetId'])
API usage with cURL
curl -X POST "https://api.apify.com/v2/acts/automation-lab~homes-co-nz-property-search-scraper/runs?token=$APIFY_TOKEN" \-H 'Content-Type: application/json' \-d '{"searchTerms":["auckland","wellington"],"maxItems":100,"searchMode":"typeahead"}'
MCP integration
Use the Apify MCP server with Claude Code, Claude Desktop, or other MCP-compatible clients.
MCP URL:
https://mcp.apify.com/?tools=automation-lab/homes-co-nz-property-search-scraper
Claude Code setup:
$claude mcp add apify-homes-co-nz https://mcp.apify.com/?tools=automation-lab/homes-co-nz-property-search-scraper
Claude Desktop JSON configuration:
{"mcpServers": {"apify-homes-co-nz": {"url": "https://mcp.apify.com/?tools=automation-lab/homes-co-nz-property-search-scraper"}}}
Example prompts:
- "Run the Homes.co.nz property search scraper for Auckland and summarize the suburbs returned."
- "Extract Wellington street candidates and create a CSV-ready table."
- "Compare result counts for Auckland, Christchurch, and Hamilton."
Data quality notes
Homes.co.nz controls the public gateway results.
Some fields are only returned for certain result types.
For example, a city result may have a city ID but no street number.
An address result may include street and number fields.
A listing or property result may include public IDs if Homes.co.nz exposes them.
Troubleshooting
If you get no rows, try broader terms such as a city or suburb.
If results look too broad, switch from typeahead to address mode.
If you need more rows, add more search terms rather than only increasing maxItems.
If centroid fields are empty, the specific result probably does not support centroid lookup.
Limits
The actor only extracts public search gateway data.
It does not access saved homes, favourites, private user accounts, admin routes, or logged-in endpoints.
It does not bypass paywalls or authentication.
Legality
This actor is designed for public data access.
Always review Homes.co.nz terms and applicable New Zealand privacy and data protection rules before using output in production.
Do not use scraped data for spam, harassment, discrimination, or other unlawful activity.
Related scrapers
Explore related Automation Lab actors for real estate and lead enrichment workflows:
- https://apify.com/automation-lab/zillow-scraper
- https://apify.com/automation-lab/realtor-scraper
- https://apify.com/automation-lab/google-maps-lead-finder
- https://apify.com/automation-lab/idealista-scraper
FAQ
Can I scrape exact Homes.co.nz addresses?
Yes. Add exact address terms and use address mode for stricter matching.
Can I scrape many New Zealand cities?
Yes. Add multiple city, suburb, or street terms and set maxItems high enough for your export.
Does this actor need a proxy?
No proxy is configured by default. The public gateway responded without proxy during development.
Does it scrape private Homes.co.nz account data?
No. The actor only calls public search and centroid endpoints.
Why are some IDs empty?
Homes.co.nz returns different fields for different result types. Empty IDs mean the gateway did not expose that ID for the row.
Changelog
Initial version extracts public Homes.co.nz search candidates with optional centroid enrichment.