Company Domain Enrichment API | CRM Firmographics avatar

Company Domain Enrichment API | CRM Firmographics

Pricing

from $1.70 / 1,000 enriched company records

Go to Apify Store
Company Domain Enrichment API | CRM Firmographics

Company Domain Enrichment API | CRM Firmographics

Enrich company domains with collision-safe, CRM-ready records: description, founding year, employee count, HQ details, funding signals, website, logo and LinkedIn context. Only unique identity matches are returned; ambiguous records are never guessed.

Pricing

from $1.70 / 1,000 enriched company records

Rating

0.0

(0)

Developer

Eugene Volper

Eugene Volper

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Categories

Share

Turn a company domain into one collision-safe, CRM-ready company record.

This Actor is deliberately strict. The identity lookup can return several companies that all echo the requested domain. It emits a dataset item only when one candidate has a unique exact company-name or LinkedIn-company-slug match to the domain label. It then joins the matched record to an exact-domain company profile from the private company database. It never chooses a lookalike result. Missing and ambiguous domains are counted in OUTPUT.json, not placed in the dataset.

Input

Provide 1–100 company domains or website URLs.

{
"domains": ["stripe.com", "https://openai.com/"]
}

Duplicate, malformed, and blank values are removed before lookup. The run summary reports their count.

Free Apify accounts receive 500 results shared across all eight Actors. The private links in SUPPORTER_ACCESS let a user submit honest feedback for 50 additional results valid for 30 days, or report a reproducible bug for 2,500 results after confirmation. No public review or positive feedback is required. Any paid Apify plan is uncapped by this internal result allowance; normal Apify platform and Actor charges still apply.

Dataset output

Every dataset record is a confirmed exact-domain match and includes:

GroupFields
Match safetyinputDomain, status, matchMethod, matchScore, candidateCount, dataCompleteness, retrievedAt
IdentitycompanyId, companyName, companyDomain, websiteUrl, linkedinUrl, logoUrl
Company profilecompanyDescription, industry, foundedYear
SizeemployeeCount, employeeSizeBand
Headquarterslocation, hqLocality, hqRegion, hqPostalCode, countryCode
Funding signalhasFunding, lastFundingRoundType, lastFundingRoundDate

dataCompleteness is a transparent percentage of the 18 populated company facts; it is not an accuracy score. A blank field means the private database did not provide that fact, or its richer profile could not be uniquely joined to the already-confirmed company identity.

Why this is safer than a field dump

The store already contains broad company-data products. This Actor competes on a reliable workflow: domain in, collision-safe selection, and a stable CRM schema. It does not claim emails, phones, contacts, revenue, total funding, tech stack, hiring, investor data, or job openings.

Pricing

Pay per enriched company record written to the default dataset. Missing and ambiguous domains are kept out of the dataset and are not charged as results. The current per-record prices reward higher Apify plan tiers:

Apify planPrice per enriched companyDiscount from Free
Free$0.00200
Bronze$0.001905%
Silver$0.0018010%
Gold$0.0017015%
Platinum$0.0017015%
Diamond$0.0017015%

Run summary

OUTPUT.json contains counts for found, notFound, ambiguous, failed, and the non-dataset status rows. This lets a bulk workflow audit misses without turning them into result rows.

Operator configuration before deployment

Set these Actor environment variables in the private Actor configuration; do not put credentials in this repository or in the dataset.

VariableRequiredPurpose
COMPANY_DATA_API_KEYYesPrivate upstream access token
COMPANY_DATA_API_BASE_URLYesPrivate company-data API base URL

Pre-launch gate — not optional

The private company-data routes are live. A Stripe schema fixture established all listed field names and revealed the domain-collision behavior. Pricing is configured privately; the Actor is not ready to publish. Before public launch, run a redacted live fixture and verify:

  1. exact response shape and field coverage for found, missing, and collision cases;
  2. the per-found-result upstream-unit count and actual balance delta for the two-query join;
  3. 100-domain latency and rate-limit behaviour; and
  4. per-found-result economics before any Apify pricing event is configured.

The code already protects result integrity. Billing uses Apify's built-in default dataset-item event, so only a delivered dataset row is charged; the Actor contains no manual Actor.charge() call and no publication mutation.