Contact Details Extractor avatar

Contact Details Extractor

Deprecated

Pricing

from $0.02 / 1,000 contact results

Go to Apify Store
Contact Details Extractor

Contact Details Extractor

Deprecated

Extract public emails, phone numbers, social profile URLs, and address candidates from website pages with robots.txt-aware fetching.

Pricing

from $0.02 / 1,000 contact results

Rating

0.0

(0)

Developer

jts

jts

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

a month ago

Last modified

Share

What this Actor does

Extract public emails, phone numbers, social profile URLs, and address candidates from website pages with robots.txt-aware fetching.

Input example

{
"urls": [
"https://example.com"
],
"ignoreRobots": false,
"maxPages": 3
}

Input fields

Provide one or more public website URLs to extract contact details from.

  • urls (array, user input): Public http:// or https:// website URLs to inspect. The Actor fetches the submitted page plus common contact/about pages on the same origin, respects robots.txt by default, and writes one extraction result per URL.
  • ignoreRobots (boolean, user input): Defaults to false. Set true only when you have authorization to fetch URLs disallowed by robots.txt.
  • maxPages (integer, user input): Fetch up to this many pages per URL: original URL, /contact, and /about. Range: 1-5.
  • apiBaseUrl (string, optional override): Override upstream API base URL. Defaults to runtime.baseUrl from service.json.

Output dataset

Each dataset item is one contact extraction response.

  • input: Submitted website URL.
  • result: Full API response with emails, phones, socials, addresses, signals, and confidence.

Developer notes

Set CONTACT_DETAILS_EXTRACTOR_API_KEY as an Apify secret environment variable. The Actor forwards it as X-API-Key to the upstream API. Use apiBaseUrl only for local or staging QA. Production runs default to the deployed API base URL from service.json. For advanced testing, a requests array can call explicit API paths; normal users should use the service-specific fields above.

Run locally

$apify run

Deploy

$apify push