Website Email & Contact Scraper - Find Emails, Phones & Socials

startUrls is required. Include/exclude patterns apply to discovered links, not the initial seeds. Use the final canonical hostname; maxPages bounds crawl work, not the number of extracted email rows.

{
  "startUrls": [
    {
      "url": "https://trustmrr.com/"
    }
  ],
  "mode": "full",
  "crawlerType": "http",
  "maxPages": 5,
  "maxDepth": 1,
  "sameDomainOnly": true,
  "includeSubdomains": false,
  "extractEmails": true,
  "extractPhones": true,
  "extractSocial": true,
  "extractLinks": true,
  "extractImages": false,
  "extractFiles": false,
  "maxConcurrency": 1,
  "requestTimeoutSecs": 30
}

• The dataset can contain page records or email records plus a summary per seed and a run summary. Use recordType when counting contacts.
• An Emails column view does not remove summary records. Published emails are not validated for deliverability or ownership.

{
  "recordType": "email",
  "seedUrl": "https://company.test/",
  "url": "https://company.test/contact",
  "email": "[email protected]",
  "depth": 1,
  "statusCode": 200
}

Fields in the documented output view

Output views select columns. They do not necessarily filter record types or exhaust the full JSON payload. Use structured JSON when you need nested arrays or objects.

These are the active public event prices checked on 2026-10-29, in USD. They describe each event, not a universal flat price for a run. Confirm your current Apify plan and run budget before starting.

A result limit and a spending cap are different controls. Account charges, applicable taxes, and separately billed providers or proxies must be considered where relevant. A cap setting is not a minimum invoice charge.

Test a small run in Apify Console, inspect its records and charges, then save a task or call the actor from your own application. Keep your Apify token in an environment variable. Source-specific credentials, if required, are separate from the Apify API token.

# Save the input example as input.json and set APIFY_TOKEN.
# This request starts an asynchronous, potentially billable run.
curl --request POST \
  'https://api.apify.com/v2/acts/whoareyouanas~website-link-scraper/runs' \
  --header "Authorization: Bearer $APIFY_TOKEN" \
  --header 'Content-Type: application/json' \
  --data @input.json

The response identifies the run. Wait for it to finish, inspect its status, and use its default dataset and key-value store to retrieve results. A successful run can still contain partial or failed records; check the output contract above before continuing downstream.