Realtor Phone Number Scraper

Realtor Phone Number Scraper — Phone Numbers from Public Pages

Realtor Phone Number Scraper finds phone numbers shown on public Realtor.com agent and broker profile pages for your keywords and chosen country. Each row returns the number in international E.164 form, the page link, its title and the public text the number appears in. Every response is structured JSON — ready to pass directly to an LLM, index into a vector store, or feed a lead-generation pipeline. No Realtor account or login is needed. Start with one keyword, then add more to cover every agent or broker you're chasing.

---

What data can I extract with Realtor Phone Number Scraper?

Using this Realtor Phone Number API, you will be able to extract the following Realtor.com phone number data:

🏢 Platform	🔎 Keyword searched	📝 Page title	📄 Public description text
🔗 Page URL	📞 Phone number (E.164)	📍 Country	🌍 Dial code

---

How to use Realtor Phone Number Scraper

Built as a real estate agent phone number scraper for brokers, mortgage teams and lead-gen tools that need to find phone numbers on Realtor.com without opening every profile by hand.

Step by step

1. Create a free Apify account.
2. Open the actor in the Apify Store.
3. Enter the keyword(s) or @usernames/realtor.com URLs, and pick a country.
4. Click Start.
5. Download or stream your results in JSON, CSV or Excel.

How to scale Realtor Phone Number Scraper to bulk

Put every keyword you want in the keywords array in one input and the actor searches up to 3 of them at the same time, each with its own maxPhoneNumbers budget (1–10,000). This realtor.com real estate phone number scraper has no separate "bulk mode" — to cover more ground, schedule repeat runs or loop API calls with a fresh keyword list each time.

---

✨ Features

Realtor Phone Number Scraper fetches clean, structured phone-number leads from Realtor.com. It's ideal for mortgage brokers, home-service businesses, relocation consultants and building an agent call list — in effect, a realtor.com phone number finder and realtor phone number lead generation tool in one.

It extracts, per result:

• Phone number – the number, normalised to international E.164 form and checked against the chosen country.
• URL – the exact Realtor.com page the number was found on.
• Title – the page title as shown in search results.
• Description – the public text the number appears in, for quick context without opening the page.
• Country / Dial code – the country you searched and its dialling code.

⚡ Checks every match against the destination country's real NANP number pattern (NXX-NXX-XXXX) before it's returned, matching Realtor.com's own "(area code) xxx-xxxx mobile/office" listing style.

---

Use cases 💡

• Mortgage broker — find phone numbers on Realtor.com for agents in a target zip code.
• Home-service business — scrape Realtor agent phone numbers before pitching a referral partnership.
• Relocation consultant — run this realtor.com contact phone number extractor across a city's agent list.
• Marketing agency — find realtor.com public phone number leads to build an outreach list for a client.
• AI agent — feed the structured JSON into a RAG pipeline so an agent can look up a broker's number on demand.

Building an AI agent? Connect this actor over MCP and let it call the actor on its own.

---

Why choose this actor?

1. Results stream in page by page, not after the whole run. A recorded local test search for "broker" in the United States returned 2 phone numbers in 18.2 seconds, written to the dataset as each result page was parsed — not held back until the run finished.
2. Built for how Realtor.com actually lists numbers. Numbers are normalised to international E.164 form and matched against the real NANP NXX-NXX-XXXX shape, the same format Realtor.com's own agent profiles use for "mobile" and "office" numbers.
3. 194 countries, one actor. Pick any of 194 countries (or Global for no country filter) and up to 10,000 phone numbers per keyword, with up to 3 keywords searched at the same time — this realtor phone number scraper by keyword covers one agent or a hundred the same way.

---

⬇️ Input

This actor accepts one or more keywords, @usernames or realtor.com URLs (reduced to the page handle) plus the country whose numbers you want. keywords and country are required.

Parameter	Required	Type	Description	Example value
keywords	Yes	array	Keywords, @usernames or realtor.com URLs. Usernames and URLs are reduced to the page handle. Each entry gets its own budget of maxPhoneNumbers; duplicates are dropped.	["broker"]
country	Yes	string (select)	Country whose phone numbers you want, from 194 countries, or Global for no filter. Every number is normalised to this country's E.164 form; numbers that cannot belong to it are dropped.	"United States (+1)"
maxPhoneNumbers	No	integer	How many phone numbers to collect per keyword, 1–10,000 (default 10). A keyword stops earlier when results run out or after 3 pages without a new number. Free plan: 20 per run in total (all keywords together), 200/month.	10
engine	No	string (select)	Processing engine. The only allowed value is legacy.	"legacy"
proxyConfiguration	No	object	Proxy used for the searches. Apify Proxy is recommended; blocked requests are retried up to 3 times, each with a new proxy session.	{"useApifyProxy": true}

Free plan limits

Users on the Apify free plan can fetch up to 20 phone numbers per run (all keywords together) and 200 phone numbers per month. When the limit is reached, the run finishes successfully with a status message explaining the limit. Upgrade to any paid Apify plan to remove these limits.

Example input

{
  "keywords": ["broker"],
  "country": "United States (+1)",
  "maxPhoneNumbers": 10,
  "engine": "legacy",
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["GOOGLE_SERP"]
  }
}

---

⬆️ Output

Every result is one typed, normalised JSON item with the same schema on every run: one row per page URL that shows a phone number of the selected country, up to maxPhoneNumbers rows per keyword, de-duplicated per keyword by URL. Export as JSON (default), CSV or Excel.

Example output

A real row from a recorded test run (keyword broker, United States):

{
  "platform": "Realtor.com",
  "keyword": "broker",
  "title": "Eric Jia - ORLANDO, FL Real Estate Agent | realtor.com®",
  "description": "Contact information (407) 401-1431 mobile 121 S ORANGE AVE STE 1430A ORLANDO, FL 32801 View map NUMBER 1 BROKER , LLC",
  "url": "https://www.realtor.com/realestateagents/5d21379bd0894300132939bf",
  "phone_number": "+14074011431",
  "country": "United States",
  "dial_code": "+1"
}

Field	Meaning
platform	The page's platform label (Realtor.com).
keyword	The keyword exactly as you entered it.
title	Page title as shown in search results (may be truncated).
description	Public text of the page as shown in search results.
url	The page URL, without tracking parameters.
phone_number	The number in E.164 form.
country / dial_code	The selected country and its dial code (empty for Global).

---

How does it work?

This actor searches the public web for Realtor.com pages that match your keyword and reads the phone number from whatever text the page's own public listing shows — it never logs into Realtor.com or opens a private page. Requests go through rotating proxies and anti-bot handling runs automatically, so a blocked attempt is retried with a fresh session instead of failing the run. Only what any logged-out visitor already sees is read: the page's title and public description text. Every number found is normalised into one consistent international format and checked against the destination country's real length and pattern before it is returned, so the output schema stays the same no matter which country or keyword you search. Realtor.com's own layout can change at any time; because the actor reads general page text rather than one fixed element, small layout changes don't automatically turn into empty rows.

---

How do you integrate Realtor Phone Number Scraper into your stack?

This actor works with what you already use: call it over the REST API from any language, or wire it into a no-code workflow tool — no extra integration layer needed.

No-code tools (n8n, Make, LangChain)

In n8n, use the Apify node's "Run an Actor" action, or the HTTP Request node pointed at Apify's run-sync endpoint with your API token. In Make, use the Apify app's "Run an Actor" module followed by "Get Dataset Items". In LangChain, install langchain-apify and call ApifyActorsTool() to let an agent run this actor and read its results directly.

---

Is it legal to scrape Realtor.com data?

Scraping publicly accessible web data is generally permitted; this actor only returns phone numbers shown on public Realtor.com pages — what any visitor sees without logging in. Using the numbers you collect to contact people is separately governed by anti-spam and telemarketing law wherever your contacts are (for example the US TCPA/CAN-SPAM rules, or GDPR and ePrivacy rules in the EU), and storing personal data must comply with the data-protection law that applies to you. Consult legal counsel if your use case involves bulk storage of personal data or contacting people found this way.

---

Frequently asked questions

What fields does Realtor Phone Number Scraper return?

It returns the phone number, the page URL, the page title, the public description text, and the country/dial code for every match. See the data fields section for the full list.

Does Realtor Phone Number Scraper require a Realtor.com account or login?

No. Only public Realtor.com page data is extracted; no credentials are needed.

How fast does Realtor Phone Number Scraper run?

There's no fixed speed limit. A local test run without a proxy found 2 phone numbers for one keyword in about 18 seconds; results on Apify's infrastructure (typically through Apify Proxy) will vary with the keyword and country.

What happens if a keyword matches no phone number?

A keyword that matches no public Realtor.com page showing a number of the chosen country simply returns no rows for that keyword — the run still ends successfully with whatever other keywords found.

Can I scrape multiple Realtor.com keywords at once?

Yes. Put every keyword in the keywords array; up to 3 are searched at the same time, each with its own maxPhoneNumbers budget, so this realtor.com agent phone number finder covers a whole roster in one run.

Does Realtor Phone Number Scraper return data in a format LLMs can use directly?

Yes. Every row is typed, normalised JSON with consistent field names — no HTML parsing, no selectors. Pass it straight to an LLM, index it into a vector store, or feed it to an agent tool with no transformation step.

What happens when Realtor.com changes its layout or anti-bot system?

This actor reads general page text rather than one fixed selector, so most layout changes don't break it outright. When Realtor.com makes a bigger change, the actor is updated and your calls keep returning the same JSON schema on your end.

Can I use Realtor Phone Number Scraper without managing proxies or browser infrastructure?

Yes. Proxy rotation and retry handling run on the actor's side. You send one request and get structured JSON back — no proxy accounts, no headless browser setup, no maintenance.

Which fields work best for AI training data and RAG indexing?

For RAG: the title and description fields are the text-rich context. For structured filtering or training data: phone_number, country and dial_code are typed strings that need no further normalisation.

---

Your feedback

Found a bug or missing a field? Let us know through the Issues tab on this actor's Apify Store page. Every report is read and feeds into the next fix.