# Approvedbusiness Email Scraper (`email_scraper/approvedbusiness-email-scraper`) Actor Approvedbusiness Email Scraper extracts publicly indexed email addresses from Approvedbusiness using targeted keywords,location filters, custom email domains, and exclusion terms. Build structured contact datasets with titles, descriptions, URLs, and emails for business research and lead generation. - **URL**: https://apify.com/email\_scraper/approvedbusiness-email-scraper.md - **Developed by:** [Email Scraper](https://apify.com/email_scraper) (community) - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $1.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 ### Approvedbusiness Email Scraper The **Approvedbusiness Email Scraper** is an Apify Actor for extracting publicly indexed email addresses associated with Approvedbusiness pages based on targeted search keywords. It helps turn search terms into a structured dataset containing the matching keyword, page title, description, URL, and discovered email address. The Actor is designed for users who need to research businesses, service providers, manufacturers, suppliers, and other relevant Approvedbusiness listings without manually reviewing search results one by one. You provide one or more keywords and can optionally narrow the search by country, state, or city. You can also specify the email domains you want to collect and exclude profiles whose descriptions contain unwanted words or phrases. Results are returned in an Apify dataset, making the collected contact information easier to review, analyze, and use in research or lead-generation workflows. ### What Is the Approvedbusiness Email Scraper? The **Approvedbusiness Email Scraper** searches publicly indexed Approvedbusiness pages using the keywords and email-domain suffixes you configure. For example, instead of searching only for a broad term such as `Manufacturer`, you can provide more specific queries such as: - `Manufacturer` - `Service Provider` - `Wholesale Supplier` - `Industrial Manufacturer` - `Local Service Provider` You can optionally provide a location to narrow the search to a particular country, state, or city. The Actor identifies matching email addresses from available search-result descriptions and returns them together with contextual information about the corresponding result. This makes the Actor useful for structured Approvedbusiness contact research, business data collection, and targeted email discovery. ### Key Features | Feature | Description | User Benefit | | ---------------------------- | --------------------------------------------------------------------- | ------------------------------------------------------------- | | Keyword-based search | Search Approvedbusiness pages using one or multiple keywords. | Target specific business categories or roles. | | Multiple keywords | Configure a list of search terms in one run. | Cover multiple search intents without separate runs. | | Location filtering | Optionally specify a country, state, or city. | Narrow research to a geographic area. | | Custom email domains | Specify domains such as `@gmail.com`, `@yahoo.com`, or other domains. | Focus collection on relevant email types. | | Per-combination email target | Configure `maxEmails` for each keyword and domain combination. | Control the amount of collection for each search combination. | | Exclusion filtering | Skip descriptions containing configured words or phrases. | Reduce unwanted matches. | | Duplicate prevention | Previously collected email addresses are tracked during the run. | Helps avoid duplicate email records. | | Structured dataset | Results are pushed into an Apify dataset. | Makes collected data easier to review and process. | | Incremental results | Matching records are added as they are collected. | Provides structured output during the run. | ### What Data Can You Extract? The Actor returns five user-facing fields for each collected contact. - **keyword** — The search keyword associated with the result. - **title** — The title of the matching Approvedbusiness search result. - **description** — The description or search-result text associated with the result. - **url** — The URL of the matching result. - **email** — The email address extracted from the available result description. The output is intentionally structured so that users can connect each discovered email address with the search context and source URL from which it was identified. The Actor does not claim that every Approvedbusiness page contains an email address. Results depend on the publicly indexed information available for the searches you configure. ### Why Use This Actor? Manually searching business directories and reviewing individual search results can become repetitive when researching multiple business categories or locations. The Approvedbusiness Email Scraper provides a configurable workflow for this type of research. You can combine multiple keywords, locations, email domains, and exclusion terms to create a search configuration that matches your research objective. For example, a business researcher could use several targeted terms rather than relying on one broad keyword. A location can then be added when the research requires geographic targeting. The resulting dataset keeps the keyword, title, description, URL, and email together, which can make subsequent review and analysis more convenient. ### Benefits The main practical benefits include: - **Automated contact research** — Reduce repetitive manual searching for publicly indexed email information. - **Targeted discovery** — Use specific keywords instead of relying on a single broad search term. - **Geographic targeting** — Narrow searches with an optional location. - **Domain targeting** — Focus searches on selected email-domain suffixes. - **Structured data** — Receive results in a consistent Apify dataset structure. - **Flexible filtering** — Exclude descriptions containing unwanted words or phrases. - **Multi-query workflows** — Process multiple search keywords in a single Actor run. - **Research-ready context** — Keep each email connected to its keyword, title, description, and URL. ### How to Use the Approvedbusiness Email Scraper The basic workflow is straightforward: 1. Enter one or more keywords in the `keywords` field. 2. Add a location if geographic targeting is required. 3. Select the email-domain suffixes you want to search for. 4. Set `maxEmails` according to the desired collection target. 5. Add `excludeWords` if certain descriptions should be skipped. 6. Start the Actor. 7. Review the resulting Approvedbusiness email dataset. For an initial test, use a small number of specific keywords and a modest email target. You can then adjust the search terms or filters based on the results. ### Input The Actor requires the `keywords` field. The other configuration fields are optional. | Field | Type | Required | Default | Description | | --------------- | ---------------- | -------- | -------------------------------------- | --------------------------------------------------------------------------------- | | `keywords` | Array of strings | Yes | `["Manufacturer", "Service Provider"]` | Keywords or queries used to search for relevant Approvedbusiness results. | | `location` | String | No | `""` | Optional country, state, or city used to narrow the search. | | `customDomains` | Array of strings | No | `["@gmail.com"]` | Email-domain suffixes to search for. | | `maxEmails` | Integer | No | `5` | Collection target for each keyword + domain combination. Allowed range: 1–10,000. | | `excludeWords` | Array of strings | No | `[]` | Words or phrases that cause a matching result description to be skipped. | #### Keywords Use specific and relevant search terms whenever possible. For example: - `Manufacturer` - `Service Provider` - `Industrial Manufacturer` - `Wholesale Supplier` Multiple keywords allow the Actor to work across different search intents in the same run. #### Location The `location` field accepts a country, state, or city as a text value. Leave it empty when you do not want a geographic filter. #### Custom Email Domains The `customDomains` field accepts multiple email-domain suffixes. Examples include: - `@gmail.com` - `@yahoo.com` - `@outlook.com` - `@company.com` The Actor searches according to the domain suffixes you provide. #### Maximum Emails `maxEmails` accepts an integer from **1 to 10,000**. The configured target applies to each keyword and email-domain combination rather than functioning as one shared target across all combinations. For example, three keywords and two domains create six keyword-domain combinations. A configured target of 20 can therefore allow collection across each combination, subject to the available indexed results and duplicate handling. On the free tier, the Actor applies a maximum of 100 collected email addresses. #### Exclude Words Use `excludeWords` to skip results whose descriptions contain unwanted terms. Single-word exclusions are matched case-insensitively as whole words. Multi-word phrases are matched case-insensitively within the description. For example: - `crypto` - `onlyfans` - `adult services` If a result description matches an exclusion term, that result is skipped and an email is not extracted from it. ### Input Example ```json { "keywords": [ "Manufacturer", "Service Provider", "Wholesale Supplier" ], "location": "London", "customDomains": [ "@gmail.com", "@outlook.com", "@yahoo.com" ], "maxEmails": 10, "excludeWords": [ "crypto", "onlyfans" ] } ``` ### Output The Actor produces structured dataset records containing the email address and contextual information associated with the matching Approvedbusiness search result. | Field | Description | | ------------- | -------------------------------------------------------------------- | | `keyword` | The keyword used to identify the result. | | `title` | The title of the matching result. | | `description` | The available description or search-result text. | | `url` | The URL associated with the result. | | `email` | The extracted email address matching the configured domain criteria. | The output is suitable for reviewing Approvedbusiness contacts, organizing research results, and building structured datasets. ### Output Example ```json { "keyword": "Manufacturer", "title": "Example Manufacturing Company", "description": "Example Manufacturing Company provides industrial manufacturing services. Contact: sales@example.com", "url": "https://approvedbusiness.co.uk/example-manufacturing-company", "email": "sales@example.com" } ``` The example values are illustrative. Actual titles, descriptions, URLs, and email addresses depend on the publicly indexed search results available during the run. ### Use Cases The Approvedbusiness Email Scraper can support several research and data-collection workflows. - **Business lead research** — Identify publicly indexed contact information associated with targeted business categories. - **Supplier research** — Search for manufacturers, suppliers, and service providers using relevant keywords. - **Market research** — Collect structured contact information for businesses within a defined category or location. - **Local business research** — Use the location field to focus searches on specific geographic areas. - **B2B research** — Combine business-oriented keywords with company email domains where appropriate. - **Business directory research** — Organize publicly indexed Approvedbusiness information into a structured dataset. - **Dataset creation** — Build datasets containing search context, source URLs, descriptions, and emails. - **Contact discovery** — Search for publicly indexed email addresses matching selected domain suffixes. ### Competitive Advantages The Actor provides several practical configuration options that can be useful for targeted Approvedbusiness research. - Multiple keyword inputs allow users to cover related search terms in one run. - Location filtering provides an optional geographic dimension. - Custom domain suffixes allow the search to focus on selected email types. - Exclusion terms provide a way to remove unwanted descriptions. - Structured output keeps the discovered email connected to its source context. - Configurable collection targets provide control over the intended amount of data. These are workflow-oriented advantages rather than guarantees about the quantity or quality of available results. ### Advantages The Actor is particularly useful when a research workflow needs configurable search criteria and structured contact output. - It accepts multiple targeted search terms. - It supports optional geographic filtering. - It supports configurable email-domain suffixes. - It provides exclusion filtering. - It returns source context alongside discovered email addresses. - It stores results in an Apify dataset. - It is suitable for repeatable research workflows. ### Limitations There are several important limitations to keep in mind. - Results depend on publicly indexed Approvedbusiness information available to the search process. - Not every Approvedbusiness result contains an email address. - A configured `maxEmails` value is a target, not a guarantee that the target will be reached. - Duplicate email addresses are not collected as separate new records. - Narrow keywords or restrictive locations may produce fewer results. - Exclusion terms can intentionally remove otherwise matching results. - The free tier applies a maximum of 100 collected email addresses. - Search availability and indexed content can change over time. For important business decisions or outreach, review and validate collected contact information before using it. ### Pros and Cons | Pros | Cons | | ------------------------------------------ | --------------------------------------------------------------- | | Supports multiple targeted keywords | Results depend on publicly indexed information | | Optional country, state, or city filtering | Narrow searches may produce limited results | | Custom email-domain filtering | Not every result contains an email address | | Exclusion words and phrases | Exclusion rules can remove matching results | | Structured five-field dataset output | `maxEmails` does not guarantee that the requested target exists | | Suitable for repeatable contact research | Duplicate email addresses are skipped | ### Comparison With Alternative Approaches | Capability | Approvedbusiness Email Scraper | Manual / Typical Alternative | | ---------------------- | ------------------------------------------- | -------------------------------------------- | | Keyword-based research | Supported | Usually performed manually | | Multiple search terms | Supported | Requires repeated searches | | Location filtering | Supported | Depends on the search workflow | | Email-domain targeting | Supported | Usually configured manually | | Exclusion filtering | Supported | Requires manual review or separate filtering | | Structured dataset | Supported | Often requires manual organization | | Source context | Keyword, title, description, URL, and email | May require manual copying | This comparison describes workflow differences rather than claiming that one approach is universally better. ### Best Practices For more targeted research, consider the following practices: - Use specific keywords rather than relying only on broad categories. - Add several related keywords when researching a business segment. - Use a location when geographic targeting matters. - Start with a small `maxEmails` value to evaluate the result quality. - Add multiple relevant email domains when broader domain coverage is needed. - Use exclusion terms only when they are genuinely useful for your research. - Review titles, descriptions, URLs, and emails before using the resulting contacts. - Broaden keywords or remove a restrictive location when results are sparse. - Increase the collection target only after confirming that the search configuration produces useful results. ### Troubleshooting **Empty results:** Try broader or more specific keywords, remove an overly restrictive location, or review the configured email domains. **Fewer emails than requested:** The `maxEmails` value is a target. The available indexed results may not contain enough matching email addresses to reach it. **Too many unwanted results:** Add relevant terms to `excludeWords` or make the search keywords more specific. **Missing email addresses:** A matching result does not necessarily publish an email address in the available indexed description. Try additional relevant keywords or email domains. **Unexpectedly limited results:** Check whether the location, keywords, email domains, or exclusion terms are too restrictive. **Free-tier limit:** Free users are limited to 100 collected email addresses by the Actor. A configured target above that level can therefore be restricted by the applicable tier limit. ### Frequently Asked Questions **What does the Approvedbusiness Email Scraper do?** It searches publicly indexed Approvedbusiness results using configured keywords and email-domain suffixes and returns matching email addresses with their associated keyword, title, description, and URL. **What keywords can I use?** You can use business-related search terms such as `Manufacturer`, `Service Provider`, `Supplier`, or other relevant phrases. More specific terms can help target a narrower research intent. **Can I use multiple keywords?** Yes. The `keywords` input is an array of strings, allowing multiple search terms in one run. **Can I target a specific location?** Yes. The optional `location` field accepts a country, state, or city and can be used to narrow the search. **Can I search multiple email domains?** Yes. The `customDomains` field accepts multiple email-domain suffixes such as `@gmail.com`, `@yahoo.com`, or `@outlook.com`. **What does `maxEmails` control?** It controls the intended collection target for each keyword and email-domain combination. It accepts values from 1 through 10,000, although available results and applicable account limits can affect the final count. **Does the Actor guarantee the requested number of emails?** No. The configured number is a target. The final number depends on the publicly indexed results and matching email addresses available for the configured searches. **What happens when I use an exclude word?** If a result description matches an exclusion word or phrase, that result is skipped and an email is not extracted from that description. **What output does the Actor produce?** Each dataset record contains `keyword`, `title`, `description`, `url`, and `email`. **Can I use the results for research and lead generation?** Yes. The structured dataset can support business research, contact discovery, supplier research, market research, and related data-collection workflows. Review and validate contacts before using them. ### NLP Keywords - Approvedbusiness Email Scraper - Approvedbusiness email extraction - Approvedbusiness contact scraper - Approvedbusiness email finder - Approvedbusiness.co.uk email scraper - Approvedbusiness lead scraper - Approvedbusiness contact extraction - Approvedbusiness business leads - Approvedbusiness professional contacts - Approvedbusiness email addresses - Approvedbusiness lead generation - Approvedbusiness contact discovery - Approvedbusiness search scraper - Approvedbusiness data extraction - Approvedbusiness public contact data - Approvedbusiness keyword search - Approvedbusiness location search - Approvedbusiness business contact data - Approvedbusiness structured dataset - Approvedbusiness research data ### Related Keywords - scrape emails from Approvedbusiness - extract emails from Approvedbusiness.co.uk - find Approvedbusiness email addresses - Approvedbusiness contact data scraper - Approvedbusiness.co.uk contact finder - Approvedbusiness lead generation scraper - Approvedbusiness business email finder - Approvedbusiness professional email finder - Approvedbusiness keyword email extractor - Approvedbusiness email lead scraper - Approvedbusiness contact research tool - Approvedbusiness email data extraction - Approvedbusiness public email discovery - Approvedbusiness business contact extraction - Approvedbusiness location-based email search - Approvedbusiness email search by keyword - Approvedbusiness email search by domain - Approvedbusiness contact dataset - Approvedbusiness lead research tool - Approvedbusiness email collection ### Final Overview The **Approvedbusiness Email Scraper** provides a configurable way to research publicly indexed Approvedbusiness contact information using keywords, optional locations, custom email domains, and exclusion terms. Its structured output contains the search keyword, result title, description, URL, and extracted email address, making the resulting dataset useful for business research, contact discovery, market research, supplier research, and structured data collection. For the most relevant results, use specific keywords, select appropriate email domains, apply location filtering only when necessary, and review the resulting dataset before using collected contact information. *Contact me:* # Actor input Schema ## `keywords` (type: `array`): A list of keywords or queries to search for. ## `location` (type: `string`): Optional country, state or city used to narrow the search. Leave it empty to search without a geographic filter. ## `customDomains` (type: `array`): List of custom email domains ## `maxEmails` (type: `integer`): How many addresses each search keyword + domain suffix combination may collect before the finder moves on to the next one. This is a per-combination target, not a run-wide total: with 3 keyword and 2 Domains and a limit of 20, the run works through all 6 combinations and aims for up to 20 addresses in each, so up to 120 overall. Lower values finish sooner and cost less; higher values dig deeper but never guarantee a fuller result, since the run can only find what is publicly listed. ## `excludeWords` (type: `array`): Words or phrases you do not want to see. ## Actor input object example ```json { "keywords": [ "Manufacturer", "Service Provider" ], "location": "", "customDomains": [ "@gmail.com" ], "maxEmails": 5, "excludeWords": [] } ``` # Actor output Schema ## `dataset` (type: `string`): No description # 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": [ "Manufacturer", "Service Provider" ], "location": "", "customDomains": [ "@gmail.com" ], "excludeWords": [] }; // Run the Actor and wait for it to finish const run = await client.actor("email_scraper/approvedbusiness-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": [ "Manufacturer", "Service Provider", ], "location": "", "customDomains": ["@gmail.com"], "excludeWords": [], } # Run the Actor and wait for it to finish run = client.actor("email_scraper/approvedbusiness-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": [ "Manufacturer", "Service Provider" ], "location": "", "customDomains": [ "@gmail.com" ], "excludeWords": [] }' | apify call email_scraper/approvedbusiness-email-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,email_scraper/approvedbusiness-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/iKLLrpvLijNgVLqhH/builds/TsChabG42JNFcTbV4/openapi.json