Dropcontact API review

Which Dropcontact calls spend a credit

Everything goes through one endpoint, /v1/enrich/all: a POST submits a batch and a GET collects it. What a contact costs depends on what you send in it.

Each email comes back with a qualification for its local part (nominative, catch_all, generic, random, invalid) and its domain (pro, perso, invalid), so nominative@pro is the result to send to. The response also names the company, cleans the first name and adds the website.

Dropcontact API pricing, plan by plan

Dropcontact API pricing is a monthly or annual subscription to a quota of emails found, in euros, on two plans that share the same ten-step ladder.

The ladder has one sweet spot and one flat stretch. 4,000 emails cost €79, only €20 more than 1,500, so the rate falls by half between those two steps. From 11,000 to 44,000 the rate barely moves, at about €0.018 an email, and it only drops again at 100,000. The 33,000 step, €599 on Starter, sits on the same flat line and is left out of the table.

Growth costs 21% more than Starter at the bottom of the ladder and 52% to 63% more from 4,000 up, for carryover, LinkedIn input and company data. The annual toggle is labeled -20%, but the annual prices work out to about 17% off, two months free: Starter at 4,000 is €66 a month billed yearly against €79 monthly.

Sixty a second, 250 contacts a request

Dropcontact API rate limits are 60 requests a second, after which the API answers 429 Too Many Requests. Each POST can carry up to 250 contacts of under 15 kB each, and the work runs asynchronously, so throughput is set as much by how quickly results come back as by the request rate.

The limits are generous for a batch API: 60 requests of 250 contacts each is far more than any plan's monthly quota can feed. What decides speed is how long a batch takes to finish, so build on the webhook from the start rather than polling.

How to create a Dropcontact API key

A Dropcontact API key is the access token in your Dropcontact account, and API access is included on every plan. Every request sends it in the X-Access-Token header, and every response reports credits_left.

One token covers the REST API and the token route into the MCP server, and both draw on the same balance. Check it before a large batch with the free empty-object POST, which reports credits left without spending any.

What a Dropcontact API call looks like

Submit a batch with a POST, then collect it with a GET on the request_id, or let a webhook deliver it. Every contact needs a company, a website or a company profile alongside the name.

# 1. submit
POST https://api.dropcontact.com/v1/enrich/all
X-Access-Token: $DROPCONTACT_KEY
# { "request_id": "...", "credits_left": 3950 }

# 2. collect
GET https://api.dropcontact.com/v1/enrich/all/{request_id}
# "Request not ready yet, try again in 30 seconds"

Where the Dropcontact API documentation lives

The Dropcontact API docs are a single reference page at developer.dropcontact.com, with Python and shell examples for every call. It covers authentication, the enrich endpoint, every request and response field, webhooks, the MCP server, the credit policy, rate limits and error codes.

The reference page is the only place that states the 60-a-second limit, the 250-contact batch and the French default. The pricing page is the only one that states the full ladder, so read the two together.

The MCP page lists Dropcontact's MCP access alongside the others in this directory.

Dropcontact's MCP server in ChatGPT, in under a minute

Dropcontact publishes this on its own channel, so it is Dropcontact's account of Dropcontact, not ours. It is here because a rate card cannot show you the thing moving, and a minute or two of the product is faster than any paragraph on this page at telling you whether the shape of it fits yours.

A 55-second demo from October 2026, on the channel Dropcontact's pricing page links. Its description lists what it shows: ChatGPT finding a contact's email and LinkedIn profile, checking whether an address is valid, and reading the credit balance, all through the MCP server. It is a demo of the connection, not of match rates, and nothing on this page about price or coverage rests on it.

Published 19 October 2026 on Dropcontact, the channel Dropcontact's own pages link to, and read on 23 October 2026. Nothing in it is a source for a price or a limit on this page: every figure in the tables above comes from a Dropcontact page.

Strengths and limits

Dropcontact is the email finder built for a legal review rather than for the biggest database.

The two columns come from the same decision. Working without a database is what makes the GDPR case and the pay-on-success rule possible, and it is also why Dropcontact needs a company for every contact and has no phone numbers to sell. It suits a list that already has names and companies and needs the emails.

Who should actually buy this

Buy Dropcontact when your legal team is part of the decision. A finder that keeps no contact database and runs on EU servers is a different conversation with a data protection officer from one that resells a profile index.

It is a good fit for a list that already has a name and a company or website per row: a CRM export, a webinar list, scraped attendees. It is not a prospecting database, so it cannot build the list for you, and it has no mobiles to add.

On price, buy the 4,000 step rather than 1,500, because it costs €20 more for 2,500 more emails, and compare the euro figure against dollar-priced finders at the day's exchange rate rather than number for number.

Before you build against it

Four things to settle first, each one read off Dropcontact's own pages. The ticks are remembered in this browser, so you can come back to a half-finished integration.

If Dropcontact is not the answer

Four providers in the Enrichment APIs listing that solve the same problem differently. Each one is a trade, and the trade is named.

The full set, organized by the reason people leave, is on the Dropcontact alternatives page.