GDPR Contact Enrichment API - Email Finder for Europe

Enrich a list of contacts or companies from whatever you already have: an email address, a professional profile URL, a company website, or a person's name paired with their employer. Every row comes back with the verified business email, the direct and mobile phone numbers, the job title, level and function, and the company behind them, including European registration data. One flat row per contact.

What this actor does

• Works from four different starting points. Addresses, profile URLs, company websites, or a name plus an employer all resolve into the same flat row shape, so lists that started in different systems end up in one table.
• Returns European company registration data, not just firmographics. Turn on the registry option and each company carries its registration number, establishment number, registered address, VAT number, activity code with its description, headcount and reported turnover. These are fields no email pattern guesser can produce.
• Qualifies every address it returns. Each address arrives with the provider's own qualification of it, and every alternative address found for the person is kept alongside the primary one, so you can apply your own sending policy rather than accepting one verdict.
• Batches properly. Up to 250 contacts go in one submission and are processed together, so a list of a thousand is four submissions rather than a thousand round trips. Each batch is written to the dataset as soon as it finishes, so a run stopped partway through still keeps everything it collected.
• Waits the way the provider asks. Submissions return a request id, not data. The actor polls with a widening gap and an overall deadline, recognises the provider's own "not ready yet" reply as a reason to keep waiting rather than a failure, and never leaves a stuck batch holding the run open.
• Matches results back safely. Results are paired to your inputs by position when the batch comes back whole, and by identifier when it does not, because attributing an enriched record to the wrong input is worse than reporting a miss.
• Never charges for a miss. Only rows carrying a resolved result are billed.

Input

Field	What it does
mode	Enrich from emails, profile URLs, company websites, or contact rows.
emails	Addresses to enrich.
profileUrls	Professional profile URLs to enrich.
websites	Company websites or domains to enrich.
contacts	Contact rows in the provider's own shape, for name plus employer.
includeCompanyRegistry	Add registration number, VAT, activity code and turnover.
language	Language for descriptive fields such as the activity description.
batchSize	Contacts per batch, up to the provider's maximum of 250.
batchTimeoutMinutes	How long to wait for one batch before giving up.
requestsPerMinute	Pace the run under your plan's rate limit.
skipNotFound	Leave unresolved contacts out of the dataset.
maxResults	Hard cap on rows, and therefore on spend and run time.
apiKey	Your own API key. Stored as a secret.

Example output

{
  "found": true,
  "mode": "customRows",
  "query": "Jane Doe at Example Labs",
  "email": "jane.doe@example.com",
  "emailQualification": "nominative@pro",
  "allEmails": [
    { "email": "jane.doe@example.com", "qualification": "nominative@pro" }
  ],
  "civility": "Ms",
  "firstName": "Jane",
  "lastName": "Doe",
  "fullName": "Jane Doe",
  "position": "Directrice Marketing",
  "jobLevel": "executive",
  "jobFunction": "marketing",
  "phone": "+33123456789",
  "mobilePhone": "+33612345678",
  "linkedin": "https://www.linkedin.com/in/janedoe",
  "organization": "Example Labs",
  "website": "example.com",
  "companyLinkedin": "https://www.linkedin.com/company/example-labs",
  "companyRegistrationNumber": "552100554",
  "companyEstablishmentNumber": "55210055400015",
  "companyRegisteredAddress": "12 Rue de Example, 75002 Paris",
  "vatNumber": "FR40552100554",
  "employees": 240,
  "activityCode": "62.01Z",
  "activityDescription": "Computer programming activities",
  "industry": "Software",
  "companyTurnover": 41200000,
  "companyResults": 3100000,
  "country": "France",
  "customFields": null,
  "error": null,
  "raw": { }
}

Frequently asked questions

What makes this different from a generic email finder?

Two things. First, the identifiers it accepts: as well as an address or a profile URL, it takes a person's name paired with their employer, which is the form most exported CRM lists are already in, and it takes a company registration number. Second, what comes back with the person: the European company register data, meaning the registration number, establishment number, registered address, VAT number, activity code, headcount and reported turnover. Most finders return an address and a job title and stop there.

Which fields identify a contact well enough to enrich it?

Any one of these combinations works: a first and last name plus a company, a full name plus a company, a professional profile URL, or an email address. Adding more than the minimum makes the match better rather than worse, so include the website, the country or the job title when you have them. In contact rows mode you can send all of them together on the same row.

What does the email qualification field mean?

It is the provider's own classification of the address it found, which distinguishes a personal work address belonging to a named individual from a generic role mailbox. It matters because the two call for completely different treatment: a nominative professional address is a person you can write to, while a generic one is a shared inbox. Every alternative address the provider found is kept alongside the primary one so you can apply your own policy.

Is this suitable for GDPR compliant prospecting?

The provider is built around European data protection practice and processes contacts in Europe, which is why it is a common choice for teams whose legal position requires it. That said, compliance is about your own basis for processing and how you use the data, not only about where it is processed. This actor gives you the provider's output; the lawful basis for contacting the people in it remains yours, and your own agreement with the provider governs what you may do with the results.

Why does a run take longer than a request to a normal API?

Because this provider is asynchronous by design. A batch is submitted, the provider works through it, and the results are collected afterwards. The actor handles all of that for you: it polls with a widening gap rather than continuously, understands the provider's own "not ready yet" reply as a reason to keep waiting, and stops on a deadline you control. The practical consequence is that bigger batches are better, not worse, since the wait is paid once per batch rather than once per contact.

Should I change the batch size?

Usually not. The default of 250 is the provider's maximum and almost always the right choice, because a batch is processed as a unit and a larger one does not take proportionally longer. Lower it only if you want partial results written to the dataset sooner, since each batch is saved as soon as it finishes.

Do I need my own API key?

Yes. This actor does not include data access. You use your own API key from Dropcontact, which is the provider whose enrichment API this actor calls, created on their dashboard. Your own plan, credit balance and terms apply. Paste the key into the apiKey field, where it is stored as an Apify secret and sent in a dedicated request header rather than a URL parameter, so it never appears in a log line or a redirect.

What happens when a contact cannot be enriched?

The row is written with found: false and an error explaining that the provider had nothing for that input, and the run continues. This provider reports an unresolvable contact inside a successful batch with its fields empty rather than as an error, so the actor recognises that shape and records it as a miss instead of treating the whole batch as failed. Misses are not charged for. Set skipNotFound to true to leave them out of the dataset entirely.

How much does a run cost?

Pricing is pay per result: you are charged for each contact or company enriched into the dataset, and never for inputs the provider could not resolve, or for duplicates. Apify platform usage is included in the per-result price. Your own API provider's credit balance is separate and billed by them.

Keyword map

GDPR email finder, contact enrichment API, B2B email finder Europe, French company data API, SIREN lookup, SIRET lookup, VAT number lookup, NAF activity code, company registry enrichment, bulk contact enrichment, mobile phone finder, direct dial lookup, CRM data enrichment, lead enrichment API, email verification, job level and function, company turnover data, headcount data, LinkedIn profile enrichment, sales prospecting data