The complete profile, fetched live.
Turn a LinkedIn URL — or a Sales Navigator ID, or just an email — into a 38-field profile and full firmographics. Read from the source at request time, never served from a cache. Typed, p50 1.2 s.
Edges is not related to LinkedIn and is not an official LinkedIn product.
// request
{
input: {
linkedin_profile_url:
"linkedin.com/in/jane-doe"
}
}// response · Profile
{
full_name: "Jane Doe",
headline: "VP Product",
job_title: "VP Product",
company_name: "Acme",
location: "SF, US",
skills: [ … ]
}- Profiles indexed
- 750M
- live · any URL
- Companies
- 54M
- domain + headcount + posts
- Median latency
- 1.2s
- p99 2.4s
- Actions
- 70+
- one runner, one key
// used by
// Schema
One predictable shape. Same envelope, every record.
Snake case, nullable rules, identifiers that join across people and companies. Generated TypeScript types ship with the SDK.
Profile · 38 fields
Company · 41 fields
// enrichment actions
Every enrichment call you'd ever make.
Each call runs through the unified runner — POST /v1/actions/{slug}/run/live — and returns typed JSON.
| Action | Endpoint | Returns | Access |
|---|---|---|---|
| Extract profileA LinkedIn profile URL → structured profile. | POSTlinkedin-extract-people | → Profile | |
| Extract contact infoA connection's phone and email. | POSTlinkedin-extract-contact | → Contact | |
| Profile activityPosts published from a profile. | POSTlinkedin-extract-people-post-activity | → Post[ ] | |
| Enrich companyA LinkedIn company page → firmographics. | POSTlinkedin-extract-company | → Company | |
| Employee countExact headcount, not a bucket. Schedule it for a trend. | POSTsalesnavigator-extract-employees-count | → Series | sales nav |
| Employees of companyEmployees from a LinkedIn company page. | POSTlinkedin-search-company-employees | → Profile[ ] | |
| Extract followersThe followers of your LinkedIn profile. | POSTlinkedin-extract-followers | → Profile[ ] | |
| Similar companiesCompanies similar to the ones you input. | POSTlinkedin-extract-similar-companies | → Company[ ] |
// Built for
Three product shapes, one enrichment API.
Same endpoints; different orchestration. The credit model means a CRM trigger and a nightly warehouse refresh share one balance.
- // sales tools
Live CRM enrichment
Trigger on lead create. Resolve URL → 38-field profile + company + headcount. Write back to Salesforce in the same request.
linkedin-extract-peoplelinkedin-extract-companywebhook - // data team
Warehouse refresh jobs
Batch enrich 10k–1M rows nightly. Async Actions with callbacks, idempotent retries, parallelism set by your tier — no babysitting cron jobs.
linkedin-extract-peoplendjsonidempotency - // AI agents
Tool-use for research
One function call returns the full typed Profile shape. Drop into your tool registry; the model reasons over structured fields.
typed schematyped sdkjsonschema
// FAQ
Enrichment, answered.
More in the docs — auth, errors, rate limits, and the full schema reference.
What is a LinkedIn enrichment API?
A LinkedIn enrichment API lets your systems send a partial identifier—often email, name plus company, LinkedIn URL, or CRM record ID—and receive back structured people or company fields (title, employer, seniority, skills, firmographics, and more) as JSON. It is the programmatic alternative to reps manually opening profiles or running one-off CSV tools.
How is LinkedIn profile enrichment different from a static database?
Static databases snapshot the web on a schedule; fields go stale when someone changes roles. An API-first enrichment flow can fetch on demand or on a cadence you control, return typed fields, and plug into the same orchestration you use for email validation or scoring. Teams usually combine both: cache what is stable, refresh what moves.
Can I enrich leads in bulk from Salesforce or HubSpot?
Yes—typical patterns are batch jobs (nightly or weekly) and real-time enrichment when a form or webhook creates a lead. You map CRM columns to API inputs, write results to custom fields, and guard with idempotency keys so retries do not duplicate work. Edges exposes LinkedIn Actions you can call from your ETL, reverse ETL, or custom workers.
What inputs do LinkedIn data enrichment APIs need?
It depends on the action: some flows start from a public profile URL, others from search-shaped filters or internal identifiers your stack already trusts. The documentation lists required and optional parameters per endpoint. Strong implementations normalize domains, dedupe people keys, and log match confidence for ops review.
Is LinkedIn enrichment the same as LinkedIn scraping?
People use both phrases for “get LinkedIn-shaped data into my app,” but scraping usually means parsing HTML or driving a browser. An enrichment API returns documented JSON and is built for automation, monitoring, and versioning—closer to how you integrate Stripe or Twilio than how you maintain a fragile parser.
How does Edges fit into an enrichment stack?
Edges is a unified LinkedIn Actions API: you choose the actions that match enrichment (often people- and company-related endpoints), authenticate once, and standardize responses across products. Pair it with your CRM, warehouse, or agent workflows. For pricing and limits, see the pricing page; for coverage, browse the action library and docs.
Who is responsible for compliance when enriching LinkedIn data?
Your organization decides permitted use cases and must follow LinkedIn’s terms, applicable privacy laws, and your contracts. Edges provides an API-oriented integration path; you should run legal and security review before high-volume or sensitive deployments.
Where should I start with Edges?
Read docs.edges.run for authentication and examples, explore edges.run/library for available actions, and book a demo on edges.run/demo if you want a guided walkthrough. The enrichment use case overview lives at edges.run/use-cases/enrichment.
Resolve your first profile in 30 seconds.
100 free credits, no card. Try every enrichment endpoint with real LinkedIn data.