Waterfall Enrichment API
Start with a LinkedIn profile URL or a person’s name and company. Find a work email, phone number or both through one enrichment workflow.
Explore Waterfall Enrichment APITargetWise products
Email and phone enrichment in one API.
The Waterfall Enrichment API finds work emails and phone numbers through 15+ data sources. Add company enrichment, reverse email lookup or prospecting when your workflow needs more context.
Choose by starting pointChoose by the identifier you have
Prospecting discovers a small candidate set; enrichment resolves one selected entity or field.
Filters or domains → filtered candidates
Known professional → work email or phone
Known company or email → business context
Product family
Choose the data your workflow needs.
Email and phone belong to one product. You choose which fields to request.
Company enrichment
Start with a website, LinkedIn page or legal identifier. Return available identity, status, location and firmographic fields.
Explore company enrichmentReverse email lookup
Start with one business email. Return available professional identity, employer and company context.
Explore reverse email lookupCompany and contact prospecting
Search company candidates or professionals at selected domains, then choose the records to enrich.
Review prospecting operationsOne delivery contract
Build once for returned, partial and unresolved outcomes.
TargetWise validates the supported identifier shape, uses the product-specific retrieval route and maps the outcome into one customer-facing contract.
Applications and agents can keep matched fields, missing fields, request identity and available provenance separate instead of treating every response as complete.
- Supported identifier validation
- Normalized field names
- Matched, partial and not-found outcomes
- Retrieval time and request ID
- Provenance state where available
Two interfaces
Use REST for application logic or MCP for agent tools.
REST suits deterministic software and automation that owns the orchestration. MCP lets an authorized AI host discover and call the same eleven operations.
Neither interface makes downstream decisions for the customer. Your application still controls field acceptance, record updates, communications and other consequential actions.
- REST API for product and workflow triggers
- MCP tools for AI-agent tasks
- Paginated search and selective enrichment
- Map results into your workflow
Evaluation
Validate the technical path before agreeing production scope.
Start with 20 emails and 5 business-phone results on the Free plan. Use contacts that represent your markets, roles and identifying information.
Review email and phone coverage separately, then check that your workflow handles complete and partial results correctly.
- Representative identifiers
- Relevant markets and fields
- Known matches and difficult cases
- Explicit no-match handling
Decision guide
Choose the product in three questions.
01Do I have a known professional and need contact fields?
02Do I have a known company and need business context?
03Do I have a business email and need identity context?
Frequently asked questions
Clear answers before you continue.
The products share a delivery layer but keep their input and output directions distinct.
Start with a real workflow
Test the product direction that matches your data.
Create a free workspace and validate the identifiers, fields, markets and delivery path that matter to you.