Reverse Contact API
Reverse Contact REST API — email-to-LinkedIn profile enrichment service that takes an email address and returns the matching LinkedIn profile, company information, and professional details, enabling agents to enrich contact records with social and professional data.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
GDPR compliant — EU-focused company. TLS enforced. No SOC2. API key with no scope granularity. Agents must ensure GDPR compliance for enriched professional contact data storage and use.
⚡ Reliability
Best When
You have email addresses and need to enrich them with LinkedIn professional data (title, company, seniority) for lead scoring or CRM enrichment.
Avoid When
You need phone numbers, mailing addresses, or consumer data — Reverse Contact is specifically LinkedIn professional enrichment.
Use Cases
- • Agents enriching CRM contact records with LinkedIn profile data (title, company, location) from email addresses
- • Lead scoring — agents using LinkedIn data fetched via Reverse Contact to qualify inbound leads by seniority and company size
- • ICP matching — agents checking if inbound email signups match ideal customer profile by enriching with LinkedIn company data
- • Email-to-company mapping — agents identifying which company an email belongs to for account-based marketing workflows
- • Data deduplication — agents finding duplicate contacts by matching email addresses to canonical LinkedIn profiles
Not For
- • Finding email addresses — Reverse Contact does the reverse (email → profile); use Prospeo or Hunter.io for email discovery
- • Consumer social enrichment — focused on professional/B2B LinkedIn data, not consumer social profiles
- • High-volume bulk enrichment — credit model becomes expensive at scale; use enterprise data providers for millions of records
Interface
Authentication
API key from Reverse Contact dashboard. Passed as X-Api-Key header. Credit-based model — each enrichment consumes credits. Single key with full account access.
Pricing
Credit-based pricing. Each email enrichment consumes 1 credit. Credits expire monthly (no rollover on most plans). Annual plans available with discount.
Agent Metadata
Known Gotchas
- ⚠ Credits consumed on every call even for emails with no LinkedIn match — agents should maintain local cache to prevent redundant API calls
- ⚠ LinkedIn data freshness varies — Reverse Contact's database may lag LinkedIn profile updates by days or weeks
- ⚠ 'Email not found' is a valid response, not an error — agents must handle both found and not-found paths explicitly
- ⚠ Personal email addresses (gmail, yahoo) rarely have LinkedIn matches — focus on professional/work emails for best match rates
- ⚠ GDPR requirements apply to how enriched data is stored and used — document legal basis for processing enriched professional data
Alternatives
Full Evaluation Report
Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Reverse Contact API.
Scores are editorial opinions as of 2026-03-06.