Skip to content
linkedindataapi.com
Migration Playbook · 20266 min read·Updated 2026-11-04

Migrating from Proxycurl to LinkedInDataAPI in 5 Minutes (Drop-In /api/v2/linkedin)

Keep your existing URL parameters and career timeline parsers while cutting person and company enrichment costs from $20–$100/1K down to $0.40–$1.00/1K.

Get Free API Key (2,000 Free Credits) →Run Live Code Example ↓

$0.40–$1.00 / 1K Profiles & Companies · $0.08–$0.20 / 1K Search Leads · 100% No-Cookie

Instant Quickstart · Copy & Run in 30 Seconds

Drop-In `/api/v2/linkedin` Compatibility Call

Execute in Live Playground →
import requests

res = requests.get(
    "https://api.linkedindataapi.com/api/v2/linkedin",
    params={"url": "https://www.linkedin.com/in/satyanadella"},
    headers={"Authorization": "Bearer b2b_live_your_api_key"},
    timeout=20,
)
profile = res.json()["data"]
print(profile["full_name"], "->", profile["headline"])

Key Engineering Takeaways (TL;DR)

  • ✓LinkedInDataAPI exposes `/api/v2/linkedin` as a native alias for `/v1/profile` so existing `?url=https://www.linkedin.com/in/...` requests work immediately.
  • ✓Both `x-api-key: b2b_live_...` and `Authorization: Bearer b2b_live_...` headers are accepted out of the box.
  • ✓Every profile response includes chronological `experiences`, `educations`, `skills`, `languages`, and current employer fields.

1. Endpoint & Parameter Mapping Table

You can either use our canonical /v1/* routes or keep your existing Proxycurl path strings during migration.

Proxycurl to LinkedInDataAPI Route & Cost Mapping
Use CaseLegacy Proxycurl RouteLinkedInDataAPI Canonical / AliasLinkedInDataAPI Cost
Person Profile LookupGET / proxycurl/api/v2/linkedin?url=...GET /v1/profile or GET /api/v2/linkedin10 Credits ($0.0004–$0.001)
Company LookupGET / proxycurl/api/linkedin/company?url=...GET /v1/company or GET /api/linkedin/company10 Credits ($0.0004–$0.001)
Employee ListingGET / proxycurl/api/linkedin/company/employeesGET /v1/people/search or GET /v1/company/employees2 Credits / person returned
Job SearchGET / proxycurl/api/v2/linkedin/company/jobGET /v1/jobs/search or GET /v1/company/jobs2 Credits / job returned

2. Side-by-Side Code Migration

Swap the base URL and API key environment variable—your Bearer token header continues to work unchanged.

Drop-In `/api/v2/linkedin` Compatibility Call

Call `/api/v2/linkedin` or `/v1/profile` with a full profile URL or username:

curl "https://api.linkedindataapi.com/api/v2/linkedin?url=https://www.linkedin.com/in/satyanadella" \
  -H "Authorization: Bearer b2b_live_your_api_key"

Interactive Engineering Workbench · GET /v1/profile

Verify real-time latency, enrichment unit math & JSON schema

2,000 profiles/day
1,000 companies/day
10,000 items/day
HTTP Calls/Day
3,400
Up to 600 RPM
Hot Cache Latency
~14 ms p50
PostgreSQL 16 + Redis
Cookie Risk
0 Cookies
No li_at required
Estimated Monthly Pipeline Cost (30 Days)
$59.70/ mo with Business bonus ($150.00 base rate)
Daily consumption: 50,000 Credits ($5.00/day)
LinkedInDataAPI (with volume bonus):$59.70 / mo
Proxycurl / Clearbit ($20+ / 1K):$6300.00 / mo
Failed / 404 request fee:$0.00 (0 Credits)
Start Free (2,000 Credits) →Full Rate Card

Frequently Asked Questions

Does LinkedInDataAPI support Bearer token authentication like Proxycurl?
Yes. You can pass either `Authorization: Bearer b2b_live_...` or `x-api-key: b2b_live_...` on all endpoints.

More engineering guides

View all guides →

CRM & Data Engineering · 2026

B2B Company & Domain Enrichment API in Python & TypeScript (2026 Guide)

8 min read →

Outbound & AI SDR · 2026

Building an Automated B2B Decision-Maker Lead Finder with /v1/people/search

7 min read →

Buying Intent Signals · 2026

Tracking Company Hiring Velocity & Technographic Buying Signals via /v1/jobs/search

7 min read →

AI Outbound Personalization · 2026

Using Executive & Company Activity Feeds (/v1/profile/posts) for AI SDR Icebreakers

6 min read →

AI Agents & MCP · 2026

Connecting LinkedInDataAPI to Claude Desktop & Cursor via Model Context Protocol (MCP)

5 min read →