By Jean-Luc Manceron, Co-founder & CTO at FullEnrich — owns the API infrastructure that powers waterfall enrichment.

What Is a Data Enrichment API?

A data enrichment API is a programmatic interface that takes partial contact or company records — a name, an email, a domain — and returns verified, structured data: work email, mobile number, job title, company size, tech stack, and more. Unlike UI-based enrichment tools where you upload a CSV and wait, an API enriches records in real time as they flow through your system — on form submit, CRM update, or webhook trigger.

The difference matters at scale. A UI tool works for 500-person lists. An API works for 50,000 leads per day, embedded in your pipeline, running without human intervention.

REST vs Webhook: Two Integration Patterns

Most enrichment APIs support two patterns:

Synchronous (REST)

Send a request, wait for the response. Simple, predictable, but slower for batch jobs. Best for single-record enrichment — a form submission, a Slack command, an AI agent tool call.

curl -X POST https://api.fullenrich.com/v2/enrich \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"first_name": "Jane", "last_name": "Doe", "company": "Acme Corp"}'

Response includes verified email, mobile, job title, company data, and the source that hit — in under 3 seconds for cached records, 10–30 seconds for waterfall lookups.

Asynchronous (Webhook)

Send a batch of records, get results pushed to your endpoint when they're ready. Best for large lists — 1,000+ records — where you don't want to hold a connection open. FullEnrich sends a webhook payload to your callback URL with each enriched record.

Authentication & Rate Limiting

FullEnrich's API uses Bearer token authentication. Your API key lives in the dashboard under Settings → API. Rate limits:

• Single enrichment: 10 requests/second
• Batch enrichment: 1,000 records per request, 5 concurrent batches
• Webhook delivery: Retries 3x with exponential backoff on failure

If you need higher throughput, the Enterprise plan unlocks custom rate limits and dedicated infrastructure.

Batch vs Single-Record Enrichment

Error Handling

The API returns structured error responses with HTTP status codes:

• 200 — Enrichment successful
• 202 — Batch accepted, processing async
• 404 — No match found (no credit charged)
• 429 — Rate limit exceeded (retry after header)
• 500 — Server error (retry with backoff)

Critical: a 404 means the waterfall exhausted all 20+ sources and found no verified match. You're not charged for this — credits are only consumed on verified hits.

The MCP Protocol: AI-Native Enrichment

Beyond REST, FullEnrich supports the Model Context Protocol (MCP) — a standard that lets AI agents call enrichment as a tool. Instead of your code calling the API, your AI agent decides when to enrich, what to enrich, and how to use the result. This is how companies like 11x went from 200M to 1.6B reachable contacts.

MCP turns enrichment from a pipeline step into an autonomous capability. The agent enriches, qualifies, and routes — all in one conversation.

When to Use the API vs the UI

• Use the API when enrichment needs to happen automatically — form submissions, CRM triggers, nightly backfills, AI agent workflows
• Use the UI when you're doing one-off list enrichment — a conference attendee list, a Sales Navigator export, a quick prospecting session
• Use both when your team mixes manual prospecting with automated pipeline enrichment

How to Evaluate Data Enrichment APIs

Coverage

The most important metric. What percentage of your target accounts and contacts does the API find? Ask for a coverage test on your actual data before committing. A provider claiming "200M contacts" means nothing if they have 12% coverage in your vertical. FullEnrich sidesteps this by cascading across 20+ providers — no single provider's coverage gap becomes your coverage gap.

Accuracy

Find rate without accuracy is noise. Measure bounce rate on enriched emails (should be under 2%) and connection rate on enriched phone numbers (should be above 40% for direct dials). Triple verification — syntax check, MX record validation, and mailbox ping — is the minimum standard.

Latency

For real-time use cases (form enrichment, chatbot qualification), response time matters. Single-source APIs typically respond in 1-3 seconds. Waterfall APIs take longer (5-30 seconds) because they query multiple sources. FullEnrich optimizes this by routing geographically — EU leads hit EU-strong providers first.

Pricing Model

Three common models: per-seat (expensive, punishes team growth), per-record (charges for misses), and per-verified-match (only charges for results). FullEnrich uses the third — you pay nothing for lookups that return no result.

Integration Patterns

CRM Sync (HubSpot, Salesforce)

The most common pattern: trigger enrichment when a new contact or lead is created in your CRM. Use native integrations (FullEnrich has HubSpot and Salesforce connectors) or build a webhook listener that fires the API on record creation. The enriched data writes back to custom fields on the same record.

Marketing Automation

Enrich form submissions before they enter your nurture sequences. A Marketo or HubSpot form captures name + email; your enrichment webhook backfills company, industry, employee count, and tech stack within seconds. The lead enters the right nurture track on the first touch.

Custom Data Pipelines

For engineering teams building proprietary lead scoring or routing: embed the API in your ETL pipeline. Pull raw leads from your data warehouse, enrich in batch via the async endpoint, write results back to a staging table, then push to your CRM or outreach tool. This pattern handles 50,000+ records per day.

Single API vs Waterfall: The Architecture Decision

Every enrichment API makes a fundamental architecture choice: query one database, or cascade across many.

If you are building enrichment into a production pipeline, the waterfall approach gives you resilience. Trusted prospecting requires infrastructure that does not go dark when one vendor has an outage.

Security Considerations

• API key rotation: Rotate keys quarterly. Never embed keys in client-side code.
• Data in transit: All API calls should be HTTPS/TLS 1.2+. FullEnrich enforces this.
• Data at rest: Enrichment results cached on FullEnrich side are encrypted and auto-expire after 30 days.
• SOC 2 compliance: Verify your enrichment provider holds SOC 2 Type II for enterprise use.
• IP allowlisting: Restrict API access to your server IP range via the dashboard.

Related Resources

• Email Enrichment — the managed waterfall for list-level enrichment
• Email Finder — single-lookup and bulk email finding
• Waterfall Enrichment — how the cascade works under the hood
• FullEnrich MCP — AI-native data infrastructure
• Waterfall Enrichment Guide — the complete technical breakdown
• Trusted Prospecting — why data accuracy is the foundation of modern prospecting

Frequently Asked Questions

What is a data enrichment API?

A data enrichment API is a programmatic interface that takes partial records (name, email, domain) and returns verified, structured data — work email, phone, job title, company info. It runs in real time as part of your pipeline, unlike UI tools that require manual uploads.

How do I integrate data enrichment into my CRM?

Most teams use Zapier, Make, or n8n to trigger enrichment on new CRM records. FullEnrich also has native HubSpot and Salesforce integrations. For custom workflows, use the REST API with webhook delivery to push enriched data back into your CRM automatically.

What is the difference between API and CSV enrichment?

CSV enrichment is batch and manual — upload a file, wait, download results. API enrichment is programmatic and real-time — your system sends records as they appear and gets results back automatically. The API is for pipelines; CSVs are for one-off lists.

How much does a data enrichment API cost?

FullEnrich starts at $29/mo for 500 credits. You pay per verified match — failed lookups cost nothing. Credits roll over up to 3 months. The API is available on all plans with no additional per-call fees.