# Realtor.ca Email Scraper (`leads-scraper/realtor-ca-email-scraper`) Actor Realtor.ca Email Scraper SD - Realtor.ca Email Scraper is a lead generation tool that extracts leads with public contact emails, account names and profile URLs from Realtor.ca results by keyword, location and email domain - Realtor.ca email extractor. - **URL**: https://apify.com/leads-scraper/realtor-ca-email-scraper.md - **Developed by:** [Leads Scraper](https://apify.com/leads-scraper) (community) - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $2.49 / 1,000 results This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README ### Realtor.ca Email Scraper: public agent emails from Canada's national listing portal The Realtor.ca Email Scraper collects contact emails that are publicly visible in Google's index alongside Realtor.ca pages. You give the Realtor.ca Email Scraper a keyword list, an optional location and the email domains you care about, and it returns a clean dataset of leads. Every row carries the email, the label Google printed for the result, the exact query that found it and a UTC timestamp. Be honest about shape before you run it. Realtor.ca indexes listing and map pages far more than agent profiles, so most rows carry an agent email without a resolvable profile URL. In a measured run of the Realtor.ca Email Scraper, roughly ten parsed result blocks produced about six unique emails and no resolvable agent handles at all. That makes the Realtor.ca Email Scraper an email-first instrument: strong for building a Canadian realtor email list, weak for building a directory of profile links. Realtor.ca is the national listing portal Canadian REALTORS use to publish inventory, and agents put a contact address on those pages on purpose. Buyers, sellers and cooperating brokers need a way to reach them, which is why a Realtor.ca email extractor works at all. If you sell to Canadian agents and brokerages, the Realtor.ca Email Scraper is the closest thing to a national, city-filterable prospecting surface. #### Who uses the Realtor.ca Email Scraper Real-estate technology vendors run the Realtor.ca Email Scraper to reach agents with CRM, IDX website, virtual staging and transaction-management products. Mortgage brokers, title and closing partners, photographers and videographers use the Realtor.ca Email Scraper to introduce local services to the agents who commission them. Recruiters and franchise development teams use it to source licensed agents by city for brokerage growth conversations. #### What the Realtor.ca Email Scraper does not do The Realtor.ca Email Scraper never logs in, never uses a Realtor.ca API and never opens the Realtor.ca website. There is no browser, no JavaScript rendering, no authentication and no cookies anywhere in the pipeline. Everything the Realtor.ca Email Scraper returns comes from publicly indexed Google search results: titles, snippets and site labels. ### Key features of the Realtor.ca Email Scraper | Feature | What it means for your realtor email list | |---|---| | Google `site:` targeting | Every query is scoped to `realtor.ca`, so leads stay on-platform | | Query expansion | Base, quoted and `intitle:` phrasings plus one variant per query modifier | | Structural parsing | Locates the `

` title then the smallest surrounding block; no reliance on Google CSS classes | | Domain-filtered extraction | Only emails ending in your `customDomains` are kept | | Global deduplication | One row per unique email across every query and page | | Email normalisation | Understands `name [at] domain [dot] com`, `name (at) domain`, `name @ domain.com`, `domain .com`, zero-width characters and the full-width at sign | | Junk filter | Rejects placeholders such as `email@`, `yourname@`, `test@`, `xxx@` and single-character locals | | Boundary-correct matching | `@gmail.com` never matches inside `@gmail.company` or `@gmail.com.br` | | Soft-wrap repair | Drops a hit that is only the tail of another email in the same block | | Concurrency pool | An `asyncio` worker pool with a shared stop signal on `maxEmails` | | Retries and block detection | Up to 3 attempts per page with exponential backoff, a fresh proxy session per request, and CAPTCHA or consent pages retried rather than counted as empty | | Requeue of failures | Blocked or failed queries are retried once at the end of the run | | Resumable state | Run state is stored in the key-value store, keyed by a hash of your input, and saved on `PERSIST_STATE`, `MIGRATING` and `ABORTING` | | Fallback parser | If Google's markup changes, the run degrades to emails without account details rather than to nothing | | Run summary | Logs pages fetched, blocked pages, retries and emails per page | ### How the Realtor.ca Email Scraper works 1. The Realtor.ca Email Scraper reads your input: keywords, location, email domains and limits. 2. It builds Google queries with the `site:` operator, for example `site:realtor.ca "real estate agent" "@gmail.com" "Toronto"`. 3. It fetches Google result pages through the Apify GOOGLE_SERP proxy using async `aiohttp` requests. 4. It parses each result block structurally rather than by CSS class name. 5. It extracts emails from the block text with a domain-filtered regex. 6. It deduplicates globally and pushes each lead to the dataset immediately, so partial results survive an abort. Base queries run before expanded ones, which means the highest-signal Realtor.ca results arrive first. If you cap `maxEmails` low, the Realtor.ca Email Scraper still gives you the best of what a Realtor.ca email extractor can reach. Because rows are pushed as they are found, you can watch the dataset fill while the Realtor.ca Email Scraper is still running. ### Input reference for the Realtor.ca Email Scraper | Field | Type | Default | Meaning | |---|---|---|---| | `keywords` | array (required) | `["real estate agent", "realtor"]` | Search terms describing the accounts you want | | `location` | string | `""` | Optional location phrase added to every query | | `customDomains` | array | `["@gmail.com","@yahoo.com"]` | Only emails on these domains are kept; the `@` is optional | | `maxEmails` | integer 1-10000 | `20` | Stop after this many unique emails | | `countryCode` | string | `""` | Two-letter country for the search proxy (US, GB, DE...) | | `expandQueries` | boolean | `true` | Search each keyword x domain pair in several phrasings | | `queryModifiers` | array | `["email","contact","listing agent","inquiries","broker"]` | Extra words combined with each keyword when expansion is on | | `maxPagesPerQuery` | integer 1-50 | `30` | Page cap per query | | `maxConcurrency` | integer 1-20 | `5` | Parallel queries | #### `location` is the highest-value input Location is the single most valuable control in the Realtor.ca Email Scraper, because Canadian agents farm neighbourhoods, not countries. Run one Realtor.ca Email Scraper job per market: `Toronto`, `Mississauga`, `Vancouver`, `Surrey BC`, `Calgary`, `Ottawa`, `Halifax`, `Winnipeg`, `Quebec City`. City-level phrases return the widest pool; neighbourhood phrases such as `Etobicoke`, `Kitsilano`, `Riverbend Edmonton` or `Le Plateau Montreal` return smaller but far more relevant sets. Keep the phrase in the form a listing page would print it. `North York` beats `North York, Ontario, Canada`, and a postal-area name usually beats a postal code. For bilingual markets, run the French phrasing as a separate job: `courtier immobilier` with `Montreal` is a different index slice than the English pair. #### `countryCode` matters here Set `countryCode` to `CA` when you run the Realtor.ca Email Scraper. It routes the search proxy through Canada and pulls the Canadian slice of the index. Leaving it empty works, but a US-weighted result set dilutes a Canadian realtor contact scraper run. #### Example input ```json { "keywords": ["real estate agent", "realtor", "listing broker"], "location": "Toronto", "customDomains": ["@gmail.com", "@yahoo.com", "@outlook.com"], "maxEmails": 300, "countryCode": "CA", "expandQueries": true, "queryModifiers": ["email", "contact", "listing agent", "inquiries", "broker"], "maxPagesPerQuery": 30, "maxConcurrency": 5 } ``` ### Output reference for the Realtor.ca Email Scraper Every dataset item produced by the Realtor.ca Email Scraper has all fourteen fields below. | Field | Meaning | |---|---| | `network` | Platform name | | `keyword` | The keyword that produced the lead | | `query` | The exact Google query used | | `title` | Raw result title | | `accountName` | Account label Google prints | | `fullName` | Display name parsed from a profile-style title; empty for listing captions | | `username` | URL-safe handle when the platform exposes one; otherwise `null` | | `profileUrl` | Canonical account URL when a handle is known; otherwise empty | | `url` | Direct platform link when exposed, else the profile URL | | `description` | Bio or caption snippet, cleaned of labels and counters | | `email` | Lower-cased email address | | `emailDomain` | The matched domain | | `possiblyTruncated` | `true` when Google's snippet ellipsis touched the email | | `foundAt` | ISO 8601 UTC timestamp | #### Example output ```json [ { "network": "Realtor.ca", "keyword": "real estate agent", "query": "site:realtor.ca \"real estate agent\" \"@gmail.com\" \"Toronto\"", "title": "Houses for Sale in Etobicoke, Toronto - REALTOR.ca", "accountName": "REALTOR.ca", "fullName": "", "username": null, "profileUrl": "", "url": "https://www.realtor.ca/on/toronto/real-estate", "description": "Contact listing salesperson directly - inquiries to jasleen.brar.realty@gmail.com for private showings.", "email": "jasleen.brar.realty@gmail.com", "emailDomain": "@gmail.com", "possiblyTruncated": false, "foundAt": "2026-08-31T09:12:44Z" }, { "network": "Realtor.ca", "keyword": "realtor", "query": "site:realtor.ca realtor contact \"@yahoo.com\" \"Toronto\"", "title": "Marc Deschenes - REALTOR.ca", "accountName": "marc-deschenes", "fullName": "Marc Deschenes", "username": "marc-deschenes", "profileUrl": "https://www.realtor.ca/agent/marc-deschenes", "url": "https://www.realtor.ca/agent/marc-deschenes", "description": "Residential sales across midtown Toronto. Email marc.deschenes.re@yahoo.com for a market evaluation.", "email": "marc.deschenes.re@yahoo.com", "emailDomain": "@yahoo.com", "possiblyTruncated": false, "foundAt": "2026-08-31T09:13:02Z" } ] ``` The first row is the common shape on this platform: a real agent email pulled from a listing or map page with `username: null` and an empty `profileUrl`. The second row is the rarer case where Google exposed an agent handle and the Realtor.ca Email Scraper could build a canonical profile link. Both rows are equally usable for outreach; only the second is usable for profile enrichment, which is the trade-off the Realtor.ca Email Scraper makes on this platform. ### Use cases for the Realtor.ca Email Scraper | Use case | How the Realtor.ca Email Scraper fits | |---|---| | Proptech and SaaS sales | Build a Canadian real estate agent email list per metro before a product launch | | Mortgage and title partnerships | Reach listing agents in the neighbourhoods where your lending or closing service operates | | Photography and videography | Introduce listing media services to agents already publishing inventory in that city | | Virtual staging and floor plans | Target agents with active listings rather than a generic agent contact database | | Recruiting and franchise development | Source licensed agents by city for brokerage growth conversations | | Transaction management and IDX vendors | Segment by keyword so brokers and salespeople land in different sequences | | Market research | Sample how many agents publish a public contact address in a given Canadian market | #### Example run recipes Three Realtor.ca Email Scraper configurations that work well in practice. Downtown Toronto condo specialists: keywords `["realtor", "condo specialist"]`, location `Toronto`, `countryCode` `CA`, `maxEmails` 200. Cross-border build: pair a Canadian run with [Homes.com Email Scraper](https://apify.com/leads-scraper/homes-com-email-scraper) for US metros, then deduplicate both datasets on `email`. Greater Vancouver farm: keywords `["real estate agent", "listing agent"]`, location `Burnaby`, domains `["@gmail.com", "@shaw.ca", "@telus.net"]`. Prairie sweep: run `Calgary`, `Edmonton`, `Saskatoon` and `Winnipeg` as four separate jobs so you can attribute reply rates per market. ### Results you should realistically expect Nothing the Realtor.ca Email Scraper returns is guaranteed, and volume moves with keywords, domains, location and what Google has indexed that week. As a calibration point, a measured run of the Realtor.ca Email Scraper returned about six unique emails per ten parsed result blocks, with zero resolvable profile URLs. Plan on an email-rich, handle-poor dataset, and do not build a workflow that requires `profileUrl` to be populated. If you need agent identity data as well as addresses, the franchise Actors are a better fit. The [Keller Williams Agent Email Scraper](https://apify.com/neuro-scraper/keller-williams-agent-email-scraper) and [Coldwell Banker Agent Email Scraper](https://apify.com/neuro-scraper/coldwell-banker-agent-email-scraper) publish real agent profile pages and return full names and profile links far more often. For Canadian coverage specifically, the Realtor.ca Email Scraper is still the broadest single source in the category. ### Responsible use Agents publish these addresses so clients and cooperating brokers can reach them, so frame Realtor.ca Email Scraper outreach as a relevant business offer, not a blast. In Canada, CASL governs commercial electronic messages, including consent, sender identification and a working unsubscribe path. If you email US recipients, CAN-SPAM applies; for EU or UK recipients, GDPR and PECR apply; phone follow-up brings TCPA-adjacent rules into play. Fair Housing principles matter in real estate outreach on both sides of the border. Do not use location targeting in the Realtor.ca Email Scraper to include or exclude people on the basis of protected characteristics. None of this is legal advice; check your own obligations before you send. ### Limitations of the Realtor.ca Email Scraper - Realtor.ca indexes listing and map pages far more than agent profiles, so most rows carry an agent email without a resolvable profile URL. This is the dominant limitation on this platform. - The Realtor.ca Email Scraper only finds addresses that are publicly visible in Google's index. An agent who hides their email will not appear. - Google caps a single query at roughly 300 results, which is exactly why query expansion exists; leave `expandQueries` on. - `possiblyTruncated: true` means Google's snippet ellipsis touched the address. Verify those before sending. - `username` and `profileUrl` are populated only when Google exposes a handle. Empty values are a Google limitation, not a bug. - The Realtor.ca Email Scraper requires the Apify GOOGLE_SERP proxy and cannot run without Apify proxy credentials. - Free Apify plans are capped at 100 emails per run; paid plans are uncapped. - Results vary with keywords, domains and location. No volume is guaranteed. ### FAQ about the Realtor.ca Email Scraper #### How many results should I expect? In a measured run the Realtor.ca Email Scraper returned about six unique emails per ten parsed result blocks, and effectively no resolvable profile URLs. Total volume depends on your keyword breadth, domain list and location, so widen all three if a run finishes short. #### Does the Realtor.ca Email Scraper log into Realtor.ca? No. It never logs in, never touches a Realtor.ca API and never opens the site. It reads publicly indexed Google results only. #### Why is `profileUrl` empty on most rows? Because Realtor.ca surfaces listing and map pages more than agent profile pages, so Google usually prints no handle to build a link from. The address is still real and usable; only the profile link is missing. #### Which email domains should I use? Start with the defaults `@gmail.com` and `@yahoo.com`, then add Canadian consumer and ISP domains such as `@outlook.com`, `@hotmail.com`, `@rogers.com`, `@shaw.ca`, `@telus.net` and `@bell.net`. Brokerage domains work too if you know the office you are targeting. #### Should I set `countryCode`? Yes, use `CA`. It routes the search proxy through Canada and keeps the result set from drifting toward US pages. #### How do I get more emails from one Realtor.ca Email Scraper run? Raise `maxEmails`, keep `expandQueries` on, add keywords such as `listing agent`, `broker` and `courtier immobilier`, and add domains. Running several narrow locations usually beats one broad national run. #### Is `maxConcurrency` safe to raise? It controls how many queries the Realtor.ca Email Scraper runs in parallel, up to 20. Higher values finish sooner and consume proxy capacity faster; 5 is a sensible default. #### What does `possiblyTruncated` mean? Google cut the snippet near the address, so the email may be incomplete. Treat those rows as needing verification rather than as clean leads. #### Can I resume an interrupted Realtor.ca Email Scraper run? Yes. State is kept in the key-value store keyed by a hash of your input and saved on Apify's `PERSIST_STATE`, `MIGRATING` and `ABORTING` events. #### What happens if Google changes its layout? A whole-page fallback parser takes over, so the Realtor.ca Email Scraper degrades to emails without account details rather than returning nothing. #### Can I export the data to my CRM? Yes. Push the Realtor.ca Email Scraper dataset to CSV, JSON or Excel from the Apify console, or pull it through the API into your CRM or outreach tool. #### Is this affiliated with Realtor.ca? No. The Realtor.ca Email Scraper is an independent Actor and is not affiliated with, supported by or endorsed by Realtor.ca or CREA. ### Related Actors | Actor | What it collects | |---|---| | [Realtor.ca Email and Phone Number Scraper](https://apify.com/neuro-scraper/realtor-ca-email-and-phone-number-scraper) | Emails and phone numbers from Realtor.ca | | [Realtor.ca Phone Number Scraper](https://apify.com/neuro-scraper/realtor-ca-phone-number-scraper) | Public phone numbers from Realtor.ca | | [Apartment List Email Scraper](https://apify.com/leads-scraper/apartment-list-email-scraper) | Public contact emails from Apartment List | | [ApartmentFinder Email Scraper](https://apify.com/leads-scraper/apartmentfinder-email-scraper) | Public contact emails from ApartmentFinder | | [Apartments.com Email Scraper](https://apify.com/leads-scraper/apartments-com-email-scraper) | Public contact emails from Apartments.com | | [Century 21 Agent Email Scraper](https://apify.com/neuro-scraper/century-21-agent-email-scraper) | Public contact emails from Century 21 | | [Coldwell Banker Agent Email Scraper](https://apify.com/neuro-scraper/coldwell-banker-agent-email-scraper) | Public contact emails from Coldwell Banker | | [CommercialCafe Email Scraper](https://apify.com/neuro-scraper/commercialcafe-email-scraper) | Public contact emails from CommercialCafe | | [CommercialSearch Email Scraper](https://apify.com/neuro-scraper/commercialsearch-email-scraper) | Public contact emails from CommercialSearch | | [Compass Agent Email Scraper](https://apify.com/neuro-scraper/compass-agent-email-scraper) | Public contact emails from Compass | | [Crexi Email Scraper](https://apify.com/leads-scraper/crexi-email-scraper) | Public contact emails from Crexi | | [Domain Agents Email Scraper](https://apify.com/leads-scraper/domain-agents-email-scraper) | Public contact emails from Domain | | [Homes & Land Email Scraper](https://apify.com/neuro-scraper/homes-and-land-email-scraper) | Public contact emails from Homes & Land | | [Homes.com Email Scraper](https://apify.com/leads-scraper/homes-com-email-scraper) | Public contact emails from Homes.com | | [HotPads Email Scraper](https://apify.com/leads-scraper/hotpads-email-scraper) | Public contact emails from HotPads | | [Keller Williams Agent Email Scraper](https://apify.com/neuro-scraper/keller-williams-agent-email-scraper) | Public contact emails from Keller Williams | | [Land And Farm Email Scraper](https://apify.com/leads-scraper/land-and-farm-email-scraper) | Public contact emails from Land And Farm | | [Land.com Email Scraper](https://apify.com/leads-scraper/land-com-email-scraper) | Public contact emails from Land.com | | [LandWatch Email Scraper](https://apify.com/leads-scraper/landwatch-email-scraper) | Public contact emails from LandWatch | | [LoopNet Email Scraper](https://apify.com/leads-scraper/loopnet-email-scraper) | Public contact emails from LoopNet | | [OnTheMarket Email Scraper](https://apify.com/leads-scraper/onthemarket-email-scraper) | Public contact emails from OnTheMarket | | [RealEstate.com.au Agents Email Scraper](https://apify.com/neuro-scraper/realestate-com-au-agents-email-scraper) | Public contact emails from realestate.com.au | | [Realtor.com Rentals Email Scraper](https://apify.com/leads-scraper/realtor-com-rentals-email-scraper) | Public contact emails from Realtor.com | | [Redfin Rentals Email Scraper](https://apify.com/leads-scraper/redfin-rentals-email-scraper) | Public contact emails from Redfin | | [RE/MAX Agent Email Scraper](https://apify.com/leads-scraper/remax-agent-email-scraper) | Public contact emails from RE/MAX | | [Rent.com Email Scraper](https://apify.com/leads-scraper/rent-com-email-scraper) | Public contact emails from Rent.com | | [RentCafe Email Scraper](https://apify.com/leads-scraper/rentcafe-email-scraper) | Public contact emails from RentCafe | | [Zillow Rentals Email Scraper](https://apify.com/leads-scraper/zillow-rentals-email-scraper) | Public contact emails from Zillow | | [Zumper Email Scraper](https://apify.com/leads-scraper/zumper-email-scraper) | Public contact emails from Zumper | | [Apartment List Email and Phone Number Scraper](https://apify.com/neuro-scraper/apartment-list-email-and-phone-number-scraper) | Emails and phone numbers from Apartment List | | [ApartmentFinder Email and Phone Number Scraper](https://apify.com/neuro-scraper/apartmentfinder-email-and-phone-number-scraper) | Emails and phone numbers from ApartmentFinder | | [Apartments.com Email and Phone Number Scraper](https://apify.com/neuro-scraper/apartments-com-email-and-phone-number-scraper) | Emails and phone numbers from Apartments.com | | [Century 21 Email and Phone Number Scraper](https://apify.com/neuro-scraper/century-21-agent-email-and-phone-number-scraper) | Emails and phone numbers from Century 21 | | [Coldwell Banker Email and Phone Number Scraper](https://apify.com/neuro-scraper/coldwell-banker-agent-email-and-phone-number-scraper) | Emails and phone numbers from Coldwell Banker | | [CommercialCafe Email and Phone Number Scraper](https://apify.com/neuro-scraper/commercialcafe-email-and-phone-number-scraper) | Emails and phone numbers from CommercialCafe | | [CommercialSearch Email and Phone Number Scraper](https://apify.com/neuro-scraper/commercialsearch-email-and-phone-number-scraper) | Emails and phone numbers from CommercialSearch | | [Compass Email and Phone Number Scraper](https://apify.com/neuro-scraper/compass-agent-email-and-phone-number-scraper) | Emails and phone numbers from Compass | | [Crexi Email and Phone Number Scraper](https://apify.com/leads-scraper/crexi-email-and-phone-number-scraper) | Emails and phone numbers from Crexi | | [Domain Email and Phone Number Scraper](https://apify.com/leads-scraper/domain-agents-email-and-phone-number-scraper) | Emails and phone numbers from Domain | | [Homes & Land Email and Phone Number Scraper](https://apify.com/neuro-scraper/homes-and-land-email-and-phone-number-scraper) | Emails and phone numbers from Homes & Land | | [Homes.com Email and Phone Number Scraper](https://apify.com/leads-scraper/homes-com-email-and-phone-number-scraper) | Emails and phone numbers from Homes.com | | [Keller Williams Email and Phone Number Scraper](https://apify.com/neuro-scraper/keller-williams-agent-email-and-phone-number-scraper) | Emails and phone numbers from Keller Williams | ### Leave a review If the Realtor.ca Email Scraper saved you time, please leave a star rating and a short review on the Actor page. Reviews are how other buyers judge whether a tool works, and they tell us which features to build next. If something did not work, email instead - bugs get fixed faster than they get complained about. ### Support Questions, a bug report or a custom build? Email neurodata.apify@gmail.com and we will help. # Actor input Schema ## `keywords` (type: `array`): Search terms describing the Realtor.ca accounts you want (niche, job title, industry). ## `location` (type: `string`): Optional location phrase added to every query (e.g. "New York"). ## `customDomains` (type: `array`): Only emails ending with one of these domains are collected. With or without the leading @. Each domain is searched separately, so more domains means more results but a longer run - remove some for a faster, narrower search, or add your own (e.g. @company.com). ## `maxEmails` (type: `integer`): Stop once this many unique emails have been collected. ## `countryCode` (type: `string`): Two-letter country code for the search proxy (e.g. US, GB, DE). Empty for any. ## `expandQueries` (type: `boolean`): Search each keyword x domain pair with several phrasings. Recommended - Google caps a single query at ~300 results. ## `queryModifiers` (type: `array`): Extra words combined with each keyword when Expand queries is on. Tuned for Realtor.ca. ## `maxPagesPerQuery` (type: `integer`): Google rarely returns more than ~30 pages for one query. ## `maxConcurrency` (type: `integer`): How many queries run in parallel. ## Actor input object example ```json { "keywords": [ "real estate agent", "realtor" ], "location": "", "customDomains": [ "@gmail.com", "@yahoo.com" ], "maxEmails": 20, "countryCode": "", "expandQueries": true, "queryModifiers": [ "email", "contact", "listing agent", "inquiries", "broker" ], "maxPagesPerQuery": 30, "maxConcurrency": 5 } ``` # Actor output Schema ## `results` (type: `string`): Records produced by Realtor.ca Email Scraper, stored in the run's default dataset. # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "keywords": [ "real estate agent", "realtor" ], "location": "", "customDomains": [ "@gmail.com", "@yahoo.com" ], "countryCode": "", "queryModifiers": [ "email", "contact", "listing agent", "inquiries", "broker" ] }; // Run the Actor and wait for it to finish const run = await client.actor("leads-scraper/realtor-ca-email-scraper").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "keywords": [ "real estate agent", "realtor", ], "location": "", "customDomains": [ "@gmail.com", "@yahoo.com", ], "countryCode": "", "queryModifiers": [ "email", "contact", "listing agent", "inquiries", "broker", ], } # Run the Actor and wait for it to finish run = client.actor("leads-scraper/realtor-ca-email-scraper").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "keywords": [ "real estate agent", "realtor" ], "location": "", "customDomains": [ "@gmail.com", "@yahoo.com" ], "countryCode": "", "queryModifiers": [ "email", "contact", "listing agent", "inquiries", "broker" ] }' | apify call leads-scraper/realtor-ca-email-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,leads-scraper/realtor-ca-email-scraper" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/eS2UHMTx0kRqZcKou/builds/zrZbFjcFmzNtCw4Ut/openapi.json