Realtor Agents Scraper
Pricing
Pay per usage
Realtor Agents Scraper
Extract realtor agent profiles, contact details, and listings at scale. Gather names, emails, phone numbers, and market data for lead generation, competitive analysis, and real estate CRM integration. Perfect for brokers, marketers & investors.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
Shahid Irfan
Actor stats
0
Bookmarked
2
Total users
1
Monthly active users
9 days ago
Last modified
Categories
Share
Extract Realtor.com agent listings in bulk, including names, broker/office details, ratings, sales activity, and pricing ranges. This scraper helps you collect agent data for lead generation, market research, and competitive analysis.
Features
- Agent profile extraction — Collect agent IDs, names, profile URLs, and avatar links.
- Performance signals — Capture ratings, review counts, testimonial counts, and recent sales activity.
- Broker and office context — Include brokerage and office names for each agent.
- Market-ready output — Export clean dataset items with pagination metadata and timestamps.
- Flexible entry points — Start from a direct Realtor search URL or build one using location and filters.
Use Cases
Agent Prospecting
Build targeted lists of active agents in specific cities. Use rating, review, and sales signals to prioritize outreach.
Brokerage Intelligence
Track broker and office visibility across local markets. Compare who appears most often in search results and where.
Market Coverage Analysis
Measure agent density and activity by location and intent. Spot markets with high competition or under-served segments.
CRM Enrichment
Feed structured agent records into CRMs and sales workflows. Keep prospect data fresh with scheduled runs.
Input Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
startUrl | String | No | Realtor New York URL | Direct Realtor agents search URL (intent/sort/agent type are read from this URL). |
results_wanted | Integer | No | 20 | Maximum agents to save. |
max_pages | Integer | No | 3 | Maximum pages to visit per start URL. |
proxyConfiguration | Object | No | { "useApifyProxy": true } | Proxy settings for higher reliability. |
Output Data
Each dataset item may include:
| Field | Type | Description |
|---|---|---|
agent_id | String | Realtor agent identifier. |
profile_url | String | Agent profile URL. |
full_name | String | Agent full name. |
broker_name | String | Brokerage name. |
office_name | String | Office name. |
avatar_url | String | Avatar image URL. |
is_realtor | Boolean | REALTOR badge indicator. |
is_paid | Boolean | Paid placement indicator. |
average_rating | Number | Average rating value. |
reviews_count | Integer | Review count. |
testimonials_count | Integer | Testimonial/recommendation count. |
for_sale_count | Integer | Active for-sale listings count. |
recent_sales_count_12m | Integer | Sales in last 12 months. |
annual_price_range | String | Price range summary. |
buyer_services | Array | Buyer-side services list. |
seller_services | Array | Seller-side services list. |
location_slug | String | Location slug from input URL. |
intent | String | Search intent for the page. |
sort_by | String | Sort mode for the page. |
rank_overall | Integer | Rank in paginated output stream. |
scraped_at | String | Extraction timestamp (UTC). |
Usage Examples
Example 1: Basic City Run
{"startUrl": "https://www.realtor.com/realestateagents/new-york_ny/intent-buy/sort-relevantagents/agenttype-all/pg-1","results_wanted": 20,"max_pages": 3}
Example 2: Build URL from Slug + Filters
{"startUrl": "https://www.realtor.com/realestateagents/miami_fl/intent-sell/sort-relevantagents/agenttype-realtors/pg-1","results_wanted": 50,"max_pages": 5}
Example 3: Larger Single-Market Pull
{"startUrl": "https://www.realtor.com/realestateagents/chicago_il/intent-buy/sort-relevantagents/agenttype-all/pg-1","results_wanted": 100,"max_pages": 6}
Sample Output
{"agent_id": "56bce3477e54f7010021e4a5","profile_url": "https://www.realtor.com/realestateagents/56bce3477e54f7010021e4a5","full_name": "Vasilis Kokoris","broker_name": "Compass","office_name": "Compass","is_realtor": true,"average_rating": 5,"reviews_count": 31,"testimonials_count": 144,"for_sale_count": 15,"recent_sales_count_12m": 42,"annual_price_range": "$180,000 - $1,425,000","location_slug": "new-york_ny","intent": "buy","rank_overall": 1,"scraped_at": "2026-03-18T10:50:00.000Z"}
Tips for Best Results
Use Stable Search URLs
- Start from exact Realtor search result URLs.
- Keep URL filters aligned with your target market and audience.
Tune Result Limits
- Use
results_wanted: 20to validate quickly. - Increase gradually for large production jobs.
Use Proxy Configuration
- Enable proxy usage for consistent page access.
- Keep concurrency moderate for stable runs.
Integrations
Connect your dataset with:
- Google Sheets — Share and review agent lists quickly.
- Airtable — Build filtered directories and outreach pipelines.
- HubSpot — Sync agent leads into CRM workflows.
- Make — Automate post-processing and enrichment.
- Zapier — Trigger alerts or downstream actions.
- Webhooks — Send results to custom services in real time.
Export Formats
- JSON — Developer-friendly structured output.
- CSV — Spreadsheet and BI workflows.
- Excel — Reporting and operations teams.
- XML — Legacy and enterprise integrations.
Frequently Asked Questions
How many agents can I collect?
You can collect as many as available across the pages you allow with max_pages, up to results_wanted.
Can I scrape multiple cities in one run?
Use one city URL per run. For multiple cities, create multiple scheduled tasks.
Why do some fields appear on some items but not others?
Some agents do not publish every metric. The scraper keeps records clean and omits empty values.
Can I target buyer-only or seller-only searches?
Yes. Use URL segments like intent-buy, intent-sell, or intent-both.
How can I reduce run time?
Keep results_wanted and max_pages small for quick runs, then scale once output looks correct.
Do I need a proxy for every run?
Not always, but proxy usage improves reliability for larger or repeated runs.
Support
For issues or feature requests, use the Apify Console issue channel for this actor.
Resources
Legal Notice
This actor is intended for lawful data collection and research workflows. You are responsible for complying with website terms and all applicable laws and regulations in your jurisdiction.