Proxycurl API
Provides compliant, structured access to LinkedIn profile and company page data via an enrichment API that abstracts the scraping complexity and delivers normalized JSON for person profiles, company pages, job listings, and school data.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Bearer token auth via header is good practice. Handles professional PII (employment, education). GDPR compliance documentation available. Single key grants full account access.
⚡ Reliability
Best When
You need high-quality structured LinkedIn data for B2B enrichment workflows and want a managed, compliant API rather than building your own LinkedIn scraping infrastructure.
Avoid When
You are cost-sensitive and need very high volumes — credits-based pricing makes large-scale enrichment expensive compared to bulk data licensing options.
Use Cases
- • Enrich a sales lead's record with full LinkedIn profile data (employment history, education, skills, connections) by providing their LinkedIn URL
- • Retrieve structured company data (headcount, description, specialties, funding) from a company's LinkedIn page URL for firmographic enrichment
- • Resolve a person's LinkedIn profile URL from their email address and name to enable downstream LinkedIn data enrichment
- • Pull current job listings from a company's LinkedIn page to monitor hiring signals for competitive intelligence agents
- • Batch enrich a list of LinkedIn profile URLs to build a prospect database with normalized, structured professional data
Not For
- • Accessing private LinkedIn profiles or connections not publicly visible on LinkedIn
- • Real-time event-driven scraping — Proxycurl caches data and freshness varies; not suitable for data needing guaranteed recency
- • Consumer applications that would expose LinkedIn data to end users without proper data handling agreements
Interface
Authentication
API key passed as a Bearer token in the `Authorization` header (`Authorization: Bearer YOUR_API_KEY`). Key obtained from the Proxycurl dashboard.
Pricing
No free tier beyond initial test credits. Credits-based model means costs scale linearly with usage. Cached data (served from Proxycurl cache) costs fewer credits than a fresh scrape.
Agent Metadata
Known Gotchas
- ⚠ Cached vs. fresh data distinction matters for cost: cached responses cost fewer credits but may be weeks old — agents must request `use_cache=if-present` deliberately
- ⚠ A 404 response means the LinkedIn profile URL is invalid or the profile has been deleted — distinct from a 404 for no enrichment data found
- ⚠ Credit consumption varies by endpoint and freshness; always check remaining credit balance before bulk operations to avoid mid-batch failures
- ⚠ The email-to-LinkedIn URL reverse lookup endpoint has lower match rates and higher cost than direct URL enrichment
- ⚠ LinkedIn data availability and structure can change when LinkedIn updates its platform — field presence in responses is not guaranteed to be stable
Alternatives
Full Evaluation Report
Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Proxycurl API.
Scores are editorial opinions as of 2026-03-06.