B2B Company Data Scraper - Website & Domain Enrichment API

Turn a company domain into structured, page-observed data for B2B lead research, CRM enrichment, domain-to-company lookup, and agent workflows. No API key or monthly subscription is required.

What it extracts

For each domain, the actor fetches the homepage and common about/contact paths, then returns:

• company name, description, and industry when reported in metadata or structured data
• public email-like strings observed in fetched page content
• phone strings explicitly published in tel: links or Organization/LocalBusiness structured data
• structured addresses
• LinkedIn, X/Twitter, Facebook, GitHub, YouTube, and Instagram links
• page title, meta description, language, logo, and favicon
• detected website technologies such as WordPress, Shopify, React, HubSpot, or Stripe
• final homepage URL, point-in-time HTTP status, and HTTPS/HTTP fetch evidence

Every returned item uses the same top-level keys, including empty strings or arrays when a field is unavailable.

First run and input

The safe default enriches one domain:

{
  "domains": ["stripe.com"],
  "maxResults": 1
}

Field	Type	Default	Description
domains	string[]	["stripe.com"]	Domains or URLs. Prefixes and paths are normalized.
maxResults	integer	1	Total maximum returned items, from 1 to 10,000.

The default costs at most $0.004. For larger lists, raise maxResults or set Apify's maximum-total-charge limit. Long runs persist results in bounded batches so completed batches are not held for one oversized dataset request.

Pricing

This actor uses pay per result:

• $0.004 per returned domain
• $4.00 per 1,000 returned domains
• no separate actor-start event in the current pricing configuration

A failed or thin website fetch still produces one structured result with statusCode and/or error, so the outcome is visible and billable rather than silently omitted.

Output example

{
  "domain": "stripe.com",
  "url": "https://stripe.com/",
  "companyName": "Stripe",
  "companyDescription": "Stripe is a financial services platform...",
  "industry": "",
  "emails": [],
  "phoneNumbers": [],
  "addresses": [],
  "socialLinkedIn": "https://www.linkedin.com/company/stripe/",
  "socialTwitter": "https://twitter.com/stripe",
  "socialFacebook": "https://www.facebook.com/StripeHQ",
  "socialGitHub": "https://github.com/stripe",
  "socialYouTube": "https://youtube.com/@stripe",
  "socialInstagram": "https://www.instagram.com/stripehq/",
  "logoUrl": "https://...",
  "faviconUrl": "https://...",
  "language": "en-US",
  "metaTitle": "Stripe | Financial Infrastructure to Grow Your Revenue",
  "metaDescription": "Stripe is a financial services platform...",
  "techStack": ["React"],
  "hasSSL": true,
  "statusCode": 200,
  "error": ""
}

Live page content changes, so exact values can differ from this example.

Evidence and limitations

This output is point-in-time website observation, not a verified company database:

• A company name, description, industry, address, or social link is publisher-reported and can be stale, incomplete, misleading, or unrelated to the legal entity operating the domain.
• Email-like strings are extracted from public page content. They are not proof of mailbox ownership, role relevance, current reachability, delivery, consent, or lawful outreach.
• Phone strings are limited to explicit tel: links and structured-data telephone fields to avoid turning arbitrary page numbers into contacts. They are not live-line or ownership verification.
• Technology detection is signature-based and can produce false positives or miss server-side/obscured tools.
• hasSSL means the actor fetched through HTTPS instead of its HTTP fallback; it is not a certificate, security, reputation, or site-safety assessment.
• HTTP status and page content reflect the actor's environment at run time, not continuous availability.
• Respect applicable website terms, privacy rules, and outreach laws when using the data.

Use legal-entity registries, verified contact providers, sanctions/licensing sources, or human review when the workflow requires identity, compliance, or contact verification.