# Company Contact Details Scraper: Emails, Phones, VAT ID (`rastriq/website-contact-extractor`) Actor

One row per company website: emails by purpose, validated phones, WhatsApp, legal name, VAT/tax id with checksum, address, Google Maps link, coordinates, booking, payments and social profiles. 40+ countries, GDPR-friendly.

- **URL**: https://apify.com/rastriq/website-contact-extractor.md
- **Developed by:** [Rastriq — Structured data from the world](https://apify.com/rastriq) (community)
- **Categories:** Lead generation, Marketing
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $6.00 / 1,000 website with data

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
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

## Company Contact Details Scraper

**Company Contact Details Scraper** is a website phone and email scraper that returns **one row per company website** — every page read is included in the price. You get everything needed to contact, identify and locate the business: emails by purpose, validated phones, WhatsApp, legal name, VAT / tax id with checksum, registered and operating address, Google Maps link and coordinates, social profiles, online booking, payment methods and more. Works in 40+ countries. GDPR-friendly by default.

- 🏢 **Company identified**: legal name, legal form, tax id (EU VAT, CIF/NIF, P.IVA, SIREN, CNPJ, RFC, ABN, GSTIN…) validated with the official check digit, trade name, register number and share capital.
- ✉️ **Emails with intent**: `purpose` (general, sales, support, privacy, jobs…), `domainMatch` (own, freemail, external). Demo, placeholder and third-party addresses never become the primary email.
- 📞 **Phones in E.164**, line type, fax flag, placeholder flag, WhatsApp (links, Joinchat, Click-to-Chat).
- 📍 **Location**: street, postal code, city, region with ISO 3166-2 code, coordinates, all branches, **Google Maps URL** (from the site's own map embeds and links — no Google scraping).
- 🛒 **Commerce**: sells online, ordering model (shop, booking, food ordering, quote…), payment methods incl. local ones (Bizum, iDEAL, Pix, OXXO, BLIK…), financing/BNPL, POS hints, delivery platforms, marketplace stores, return/shipping policies.
- 🔒 **Privacy by design**: most mailboxes that name a person and the identity of sole traders are withheld unless you switch them on.
- ✅ **Optional official verification** (paid add-on): VIES, GLEIF, BrasilAPI, Companies House.
- 🗺️ **Plugs into Google Maps scrapers**: give it a dataset id and it enriches every place with a website.

### What is Company Contact Details Scraper?

Company Contact Details Scraper is a contact details scraper and email extractor for company websites. Give it a list of websites (or a Google Maps dataset) and it returns, per site, the primary email, phone, WhatsApp, social profiles, legal name and **VAT number** or tax id, so you can build lead lists without opening each site.

### How it works

For each website it reads the **home page, the legal pages** (legal notice, imprint, privacy, terms) **and the contact page** (plus up to 5 extra pages if you raise *Extra pages per site*) — plain HTTP first, a real browser only when a site blocks or renders everything with JavaScript. Identity is resolved from the tax id and the legal-form names on those pages; third parties (hosting providers, payment partners, insurers, web agencies, shareholders) are recognised and ignored. One fixed price per website, whatever the number of pages.

### How to use Company Contact Details Scraper

1. Paste company websites in **Websites** (or the id of a Google Maps run in **Input dataset**). The 3 pre-filled websites cost about $0.03.
2. Leave the other options as they are; raise **Extra pages per site** (up to 5) for more addresses and branches.
3. Click **Start** and open the **Output** tab: the *Overview* view shows company, tax id, email, phone, city and flags; other views show contacts, identity, location and commerce. Download as JSON, CSV or Excel.
4. Sites that block or do not answer are not charged; see the `FAILED_URLS` record in the run's key-value store.

### Input

| Field | What it does | Default |
|---|---|---|
| `startUrls` | Websites or bare domains (use this, an input dataset, or both) | – |
| `datasetId` / `datasetField` | Read websites from a dataset (e.g. Google Maps results) | `website` |
| `passthroughFields` | Dataset fields copied to `inputRef` for joins | `title`, `placeId` |
| `contactMaxPages` | Extra pages besides home + legal (1 = contact page; up to 5 adds about / locations / team) | 1 |
| `includePersonalEmails` | Emit mailboxes that name a person | off |
| `includePersonalData` | Emit name, personal tax id and registered address of sole traders | off |
| `verifyIds` | Official registry check (separate event) | off |
| `crawlerType` | `adaptive` / `http` / `browser` | adaptive |
| `maxConcurrency` | Websites processed in parallel (1-50) | 10 |
| `respectRobotsTxt` | Skip legal/contact pages that robots.txt disallows | on |
| `pageTimeoutSeconds` | Timeout per page request (10-180 s) | 45 |
| `proxyConfiguration`, `fallbackProxyConfiguration` | Main proxy and optional proxy for blocked sites. With Apify datacenter/automatic proxy, a site that blocks or does not answer is first retried from 2 new IPs at no extra cost; the fallback (e.g. Residential) is used only if it still blocks | Apify Proxy, no fallback |

### Output (main fields)

| Group | Fields |
|---|---|
| Record | `inputUrl`, `domain`, `finalUrl`, `inputRef`, `status` (ok / partial), `siteCountry`, `htmlLang`, `fetchMethod`, `scrapedAt`, `pagesScanned` |
| Identity | `companyName`, `companyNameEvidence`, `tradeName`, `legalForm`, `holderType`, `taxId`, `taxIdType`, `taxIdCountry`, `taxIdChecksumValid`, `ids[]`, `registeredAddress`, `commercialRegister`, `registerType`, `registerNumber`, `shareCapital`, `personalDataWithheld[]` |
| Contact | `emailPrimary`, `phonePrimary`, `whatsappPrimary`, `emails[]`, `phones[]`, `whatsapp[]`, `whatsappBusinessLink`, `personalEmailsWithheld`, `privacyEmail`, `contactPageUrl`, `contactForm`, `formProviders[]`, `chatWidgets[]`, `openingHours[]`, `emailProvider`, `hasMx` |
| Social | `linkedin`, `facebook`, `instagram`, `x`, `youtube`, `otherSocial[]` (TikTok, Pinterest, Telegram, Messenger…) |
| Location | `city`, `postalCode`, `admin2`, `admin1`, `admin1Code`, `countryCode`, `latitude`, `longitude`, `geoPrecision`, `locations[]`, `locationsCount`, `serviceArea[]`, `googleMapsUrl`, `googleMaps[]` |
| Profile | `businessCategory` (schema.org), `description`, `logoUrl`, `foundingYear`, `copyrightYear`, `languages[]`, `cms`, `onlineBooking[]`, `reviewProfiles[]`, `careersUrl` |
| Commerce | `sellsOnline`, `orderingModel[]`, `offersFinancing`, `ecommerce` {platform, paymentMethods, paymentGateways, posProvider, deliveryPlatforms, marketplaceStores, omnichannel, currency, policyUrls…} |
| Extra | `profile` {businessModel, audience, mobileApps, atsVendor, aggregateRating (self-declared), trustSeals, saasFromDns, dmarcPolicy}, `idVerification[]`, `dataQualityFlags[]` |

Nothing is filtered for quality: doubtful values are kept and flagged (`dataQualityFlags`, `checksumValid`, `placeholderLikely`, `matchesCompany`, `nameMatches`…), so you decide.

`openingHours[]` uses one format: `"Mo-Fr 09:00-13:00,14:00-19:00"`, `"Sa 10:00-15:00"` (days with the same hours grouped, 24 h = `00:00-24:00`); text that cannot be read is kept as written. Some `dataQualityFlags`: `STREET_SUSPECT` (street still very long after cleanup), `CITY_NOT_IN_POSTAL` (GeoNames does not list that city for the postal code), `TRADE_NAME_FROM_TITLE` (trade name only from the page title), `OPENING_HOURS_ASSUMED_24H` (`00:00-00:00` read as open 24 h), `ONLY_EXTERNAL_EMAILS` (the primary email is on another domain), `PHONE_COUNTRY_MISMATCH`, `NAME_WITHOUT_ID_ANCHOR`.

#### Example (shortened, real output)

```json
{
  "domain": "mercadona.es",
  "status": "ok",
  "companyName": "Mercadona S.A",
  "tradeName": "Mercadona",
  "legalForm": "SA",
  "taxId": "A46103834",
  "taxIdType": "ES_CIF",
  "taxIdChecksumValid": true,
  "phonePrimary": "+34800500220",
  "linkedin": "https://www.linkedin.com/company/mercadona",
  "instagram": "https://www.instagram.com/mercadona/",
  "otherSocial": [{ "platform": "tiktok", "url": "https://www.tiktok.com/@mercadona" }],
  "city": "Valencia",
  "postalCode": "46135",
  "admin1Code": "ES-VC",
  "countryCode": "ES",
  "latitude": 39.5333,
  "longitude": -0.35,
  "geoPrecision": "postal-code"
}
```

### Pricing

Pay per event, no subscription:

| Event | Price | When |
|---|---|---|
| Actor start | $0.005 | once per run |
| Website with data | $0.008 (volume tiers: Silver $0.007, Gold $0.006) | one per row in the dataset, whatever the number of pages read |
| ID verification (optional) | $0.005 | only for websites where an official registry answered |

Blocked or unreachable sites are **not charged**; they are listed in the `FAILED_URLS` key-value record with the reason, e.g. `unreachable (home 403)`. A row with `status: partial` (the page loaded but little or no data was found) is a normal row and is billed. The default run (3 websites) costs about $0.03 in total. 1,000 websites cost about $8 — one flat row per website, instead of one billed row per page.

### Limits worth knowing

- The default run timeout is 600 seconds (10 minutes). For lists of several hundred websites raise the timeout in the run options.
- Tax ids are only found when the site publishes them: common in the EU and on larger Latin American sites; small businesses in Latin America, the US, the UK and Japan rarely publish one, so expect `taxId` empty there.
- Contact channels differ by country. Many small businesses in Brazil and Mexico (and much of Latin America) are one-page sites that use **WhatsApp** instead of a contact page or email: check `whatsappPrimary` / `whatsapp[]` before treating `contactPageUrl` or `emailPrimary` as missing. Japanese small businesses usually offer a contact form rather than an email (`contactForm`).
- Payment gateways and POS systems are only visible when they appear outside the checkout; when not visible the field is empty, which does not mean "none".
- Postal-code geocoding uses GeoNames; `geoPrecision` tells whether coordinates are the site's own (`exact`), the postal-code centroid (`postal-code`) or the centroid of the city (`city`, from the offline GeoNames city gazetteer when the site gives a city but no postal code or map pin). `CITY_FROM_TEXT` in `dataQualityFlags` marks a city found by name in the address text (no postal code), checked against that gazetteer.

### FAQ

**How is this different from a plain email scraper?** It identifies the company behind the site (legal name, tax id with checksum, address, coordinates) and returns phones in E.164 with line type, emails classified by purpose, WhatsApp and social profiles in one flat row per website.

**Why is one website one row?** Each row merges the home page, legal pages, contact page and up to 5 extra pages. You are billed once per website, not once per page.

**Does it return personal emails?** Not by default: most mailboxes that name a person (`laura.gomez@`, `jason@`) are withheld and counted in `personalEmailsWithheld`; an occasional personal address can still slip through unclassified. Switch on `includePersonalEmails` only if you have a legal basis.

**What if a website blocks the run?** Plain HTTP is tried first, then a browser, then 2 fresh datacenter IPs and finally your optional fallback proxy (e.g. Residential). Sites that still fail are not charged and appear in `FAILED_URLS`.

**What if a run finds no results?** If a run finds no results, it ends with status FAILED and a message explaining the likely cause (how many websites failed, with the per-URL reasons in `FAILED_URLS`), so empty runs are never silent.

**Can I feed it from a Google Maps run?** Yes: pass the dataset id in `datasetId`; `passthroughFields` are copied to `inputRef` so you can join the results back.

**Is it legal to scrape company websites?** The Actor reads only public business information from the pages of each site (home, legal and contact pages) and respects `robots.txt` by default. Personal mailboxes and sole-trader identities are withheld unless you switch them on; you are responsible for having a legal basis for how you use the data (see *Privacy*).

**Do I need proxies?** No. Apify datacenter proxy is on by default; add a fallback proxy such as Residential only if many sites come back blocked (proxy traffic is billed by Apify separately).

**Can I call it from the API or an AI agent?** Yes, it is a regular Actor: run it through the Apify API, the Apify MCP server, Make, n8n or Zapier. See the MCP section below.

### Use with Claude/ChatGPT (MCP)

Company Contact Details Scraper works with the Apify MCP server, so an AI assistant can run it for you.

- **Hosted server (all Actors):** `https://mcp.apify.com`
- **Only this Actor:** `https://mcp.apify.com?tools=actors,rastriq/website-contact-extractor`
- **Local client:** `npx @apify/actors-mcp-server --tools rastriq/website-contact-extractor` with your `APIFY_TOKEN` set as an environment variable.

Example prompts:

- "Get the primary email, phone and VAT number of example.com and example.co.uk."
- "Take these 20 agency websites and list which ones publish a WhatsApp number."
- "For each of these online stores, return the company name, tax id and whether the checksum is valid."

### Related Actors

- [Website Legal Entity Extractor](https://apify.com/rastriq/legal-entity-extractor) (`rastriq/legal-entity-extractor`): a broader website audit. Besides the company CIF/NIF or EU VAT ID and legal name, it covers tech stack, cookie consent, security headers, SEO and social profiles. Choose it for compliance or audit work. Choose **Company Contact Details Scraper** when you want flat contact rows (emails by purpose, E.164 phones, WhatsApp, address, coordinates) plus the tax id, billed once per website.

### Data sources & attribution

Postal codes, cities and places: [GeoNames](https://www.geonames.org/) (CC BY 4.0). Verification: VIES (European Commission), GLEIF, BrasilAPI, Companies House.

### Privacy

Only public business information is collected. Personal mailboxes and the identity of natural persons (sole traders) are withheld by default; partner/director data returned by registries is never emitted. You are responsible for having a legal basis (e.g. GDPR legitimate interest) for how you use the data.

# Actor input Schema

## `startUrls` (type: `array`):

Company websites or bare domains, one per line, e.g. <code>https://www.example.com</code> or <code>example.co.uk</code>. For each site the Actor reads the home page, its legal pages and the contact page (plus the extra pages you choose below). You can combine this with an input dataset.

## `datasetId` (type: `string`):

Enter the id of a dataset (e.g. a Google Maps scraper run). Every item with a website in <b>Website field</b> is processed and the fields in <b>Fields to keep</b> are copied to <code>inputRef</code> so you can join the results back.

## `datasetField` (type: `string`):

Field of the input dataset that holds the website URL. Nested fields with a dot: <code>contact.website</code>.

## `passthroughFields` (type: `array`):

Fields of the input dataset copied to <code>inputRef</code> in each result (for joins).

## `contactMaxPages` (type: `integer`):

Pages read besides the home page and the legal pages. <b>1</b> = contact page only (default, cheapest in time). Up to <b>5</b> also reads about-us, locations and team pages (more addresses and branches). The price per website does not change.

## `includePersonalEmails` (type: `boolean`):

Emit mailboxes that name a person (<code>laura.gomez@</code>, <code>j.martin@</code>). Off by default: they are counted in <code>personalEmailsWithheld</code>. Personal data under GDPR — make sure you have a legal basis before enabling it.

## `includePersonalData` (type: `boolean`):

When the business belongs to a natural person (sole trader / autónomo / Einzelunternehmer), emit their name, personal tax id and registered address. Off by default: those fields are empty and listed in <code>personalDataWithheld</code>. Company data is always emitted.

## `verifyIds` (type: `boolean`):

Check the tax ids found against <b>VIES</b> (EU VAT), <b>GLEIF</b> (LEI) and <b>BrasilAPI</b> (CNPJ); UK company numbers against <b>Companies House</b>. Adds the official name, address, status and whether the name matches the website.

## `crawlerType` (type: `string`):

<b>Adaptive</b>: plain HTTP first, a real browser only for blocked or JavaScript-only sites (recommended). <b>HTTP</b>: cheapest, no browser. <b>Browser</b>: always render.

## `proxyConfiguration` (type: `object`):

Proxy for the website requests. Apify Proxy (automatic) works for most sites.

## `fallbackProxyConfiguration` (type: `object`):

Optional. Sites that block the main Apify datacenter proxy are first retried from 2 new IPs (free). This proxy (e.g. Residential) is used only if they still block. Leave empty to skip.

## `maxConcurrency` (type: `integer`):

Websites processed in parallel. Lower it if many sites come back blocked.

## `respectRobotsTxt` (type: `boolean`):

Skip legal/contact pages disallowed by the site's robots.txt.

## `pageTimeoutSeconds` (type: `integer`):

Timeout for each page request, in seconds.

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://www.heise.de"
    },
    {
      "url": "https://www.mercadona.es"
    },
    {
      "url": "https://www.otto.de"
    }
  ],
  "datasetId": "aBcD1234eFgH5678",
  "datasetField": "website",
  "passthroughFields": [
    "title",
    "placeId"
  ],
  "contactMaxPages": 1,
  "includePersonalEmails": false,
  "includePersonalData": false,
  "verifyIds": false,
  "crawlerType": "adaptive",
  "proxyConfiguration": {
    "useApifyProxy": true
  },
  "maxConcurrency": 10,
  "respectRobotsTxt": true,
  "pageTimeoutSeconds": 45
}
```

# Actor output Schema

## `websites` (type: `string`):

One row per website: company identity, contacts, location and commerce signals.

# 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 '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "startUrls": [
        {
            "url": "https://www.heise.de"
        },
        {
            "url": "https://www.mercadona.es"
        },
        {
            "url": "https://www.otto.de"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("rastriq/website-contact-extractor").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 '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "startUrls": [
        { "url": "https://www.heise.de" },
        { "url": "https://www.mercadona.es" },
        { "url": "https://www.otto.de" },
    ] }

# Run the Actor and wait for it to finish
run = client.actor("rastriq/website-contact-extractor").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 '{
  "startUrls": [
    {
      "url": "https://www.heise.de"
    },
    {
      "url": "https://www.mercadona.es"
    },
    {
      "url": "https://www.otto.de"
    }
  ]
}' |
apify call rastriq/website-contact-extractor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,rastriq/website-contact-extractor"
        }
    }
}
```

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 <APIFY_API_TOKEN>` 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/ylyhYOgEpMfaNM4ZM/builds/eS4JCsWPsxbytNW2y/openapi.json
