Reference & Lookup Data · Integration
Dropcontact
Add Dropcontact to your product for your customers, and give your AI agents governed access to it.
Dropcontact is asynchronous by design and there is no synchronous enrichment call. You POST to api.dropcontact.io/batch with an X-Access-Token header and a data array of up to 250 contacts, receive a request_id, then poll GET /batch/{request_id} until the result is ready; polling too early returns a not-ready response rather than an error, so retry logic has to distinguish the two. Input fields are loose on purpose: you can supply any mix of full_name, first_name, last_name, email, company and website, and Dropcontact fills the gaps. Because it is a French company built around GDPR, it computes and verifies addresses rather than serving them from a stored database, and it returns French legal identifiers such as SIREN and NAF codes on company records, which most enrichment vendors do not. Credits are consumed on results, and a batch that finds nothing costs little, which changes how you budget retries. fastn holds each customer's own access token, manages the polling loop, and keeps credit usage attributed per tenant.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Dropcontact token so enrichment in your product runs against their credit balance, not yours
Enrich signup records with verified work email and company website before they reach the customer's CRM
Batch clean an imported contact list, normalising names and civility before writing it into your own data model
Pull SIREN and NAF codes onto French company records for customers who need legal identifiers on file
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent submit an enrichment batch and report which rows resolved, with token use and credit spend audited per tenant
Have an agent verify a single contact's email before an outbound sequence adds them
Allow an agent to explain why a contact came back without an email rather than silently dropping it
Example prompt
Enrich these twelve contacts with Dropcontact and tell me which ones came back without a verified email.
Set up Dropcontact in 4 steps
- 01Enable the Dropcontact connector from your fastn dashboard.
- 02Have each customer authorise their own Dropcontact account, so calls run under their credentials rather than a shared key.
- 03Decide which lookups, results and reports your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Dropcontact integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Dropcontact integration without building it. Your customers connect their own Dropcontact account inside your product and work their lookups, results and reports there, with no per-customer code on your side.
- Handle the part that actually costs time: these are metered read sources, so an uncached lookup on every page view burns the customer's allowance. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Dropcontact update is not your on-call problem.
- One integration serves your product and your agents. The same governed Dropcontact connection powers in-product features and gives AI agents scoped, audited access, so you answer questions from an authoritative outside source without holding that data yourself without wiring it twice.
Used by these teams
Compare with
Clearbit
APIVoidOften used alongside
Tools the same teams tend to run next to Dropcontact, across other categories.
Salesforce
HubSpot
Notion
SnowflakeDropcontact integration FAQ
How do I add a Dropcontact integration to my product?
Enable the Dropcontact connector in your fastn dashboard, then let each customer authenticate their own Dropcontact account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Dropcontact client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Dropcontact account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Dropcontact account and only ever sees their own lookups, results and reports. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Dropcontact integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent submit an enrichment batch and report which rows resolved, with token use and credit spend audited per tenant
Who maintains the Dropcontact integration?
fastn does. When Dropcontact changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose credentials does a Dropcontact lookup run under?
Each customer's own. Quota and cost land on the customer that caused them rather than on a shared key you have to meter and re-bill, and one heavy customer cannot exhaust another's allowance.
How should Dropcontact results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. Dropcontact is a read source rather than a system of record, so the same query returns the same answer until the source changes, and caching is the difference between a sustainable integration and one that exhausts a customer's allowance on a busy page.
What can I build with the Dropcontact integration?
A common starting point: let a customer connect their own Dropcontact token so enrichment in your product runs against their credit balance, not yours. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Dropcontact integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Dropcontact does not change your per-connector cost. You can start free with 3 connected accounts.
Add Dropcontact to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.