Refresh CRM records
Turn a known LinkedIn profile or company URL into structured research for your CRM.
20 credits per profile + 1 per company
See the workflowFind people. Enrich CRM records. Research company teams and post engagement. Get structured data through 16 focused API actions.
100 free credits on verified signup · Managed access · REST + JSON
16implemented data actions
1 creditstandard person lookup
20 creditsfull profile enrichment
REST + JSONlive and async runs
WHAT YOU CAN BUILD
Bring LinkedIn research into your CRM, product, or internal tools. Each workflow below maps to implemented actions and explains which steps your application handles.
Turn a known LinkedIn profile or company URL into structured research for your CRM.
20 credits per profile + 1 per company
See the workflowLook up a named person at a known company without opening their LinkedIn profile.
1 credit for a returned match
See the workflowDiscover people with Sales Navigator keyword search, then enrich the records you select.
1 credit per search row; optional profiles cost 20 each
See the workflowFind relevant posts and collect the available context about their commenters and reactors.
1 credit per post, comment, or reaction
See the workflowCompare successive person or company reads to flag changes for your team.
Each new read is billed at the action’s normal rate
See the workflowUse one REST interface for source reads instead of maintaining your own collection scripts.
1 credit per returned row, except full profiles at 20
See the workflowSTANDARD PERSON DATA
Supply a first name, last name, and current company. Get a matching Sales Navigator person record without visiting the profile. Request full enrichment separately when you need experience, education, or skills.
Ambiguous or incomplete matches fail without charging. An optional public profile URL helps distinguish namesakes.
Read the lookup contractcurl "$API_URL/v1/actions/salesnavigator-search-person/run/live" \
-H "Authorization: Bearer $API_KEY" \
-H "Idempotency-Key: person-lookup-001" \
-H "Content-Type: application/json" \
-d '{
"input": {
"first_name": "Satya",
"last_name": "Nadella",
"company": "Microsoft"
},
"max_results": 1,
"max_credits": 1
}'16 ACTIONS. ONE RUN INTERFACE.
Every action supports live and asynchronous execution. Use a Bearer API key, an idempotency key, and an explicit credit budget.
MANAGED ACCESS
Use our managed access for the 16 read actions. You do not need to supply LinkedIn credentials or a Sales Navigator subscription.
Submit a keyword, supported LinkedIn identifier, or name-and-company lookup. The backend schedules approved scraping sources, manages rate pacing, and delivers structured JSON output.
Your application manages its own scheduling, data storage, record matching, and notifications. We do not provide outreach endpoints, messaging, or CRM connectors.
WHAT THE RESPONSE CONTAINS
Use search rows for a person’s current role, richer profile reads for professional history, and company reads for business context. Missing source fields are omitted.
Search provides current-position data. Full enrichment adds available profile sections.
Connection degree is relative to the source account. Full-history completeness and private contact details are not guaranteed.
Read website, industry, company description, and available workforce and location fields.
Funding rounds, affiliates, follower identities, and employee distributions are not returned by the current company action.
FROM A READ TO A WORKFLOW
Use the same action inputs in either execution mode. Add your own scheduler and application logic for recurring research.
LIVE + ASYNC
Live calls attempt execution immediately; busy requests can return 202. Async calls queue work. Poll the run until it completes or fails.
See how it worksYOUR APPLICATION
Schedule fresh person or company reads, store observations, and compare available fields. Your code owns schedules, diffs, and notifications.
See how it worksYOUR APPLICATION
Collect commenters, enrich selected profile URLs, filter the returned context, and write it to your CRM. Sending outreach belongs in a separately authorized system.
See how it worksNative schedules, completion webhooks, automatic pagination, and a workflow builder are not implemented.
THE INTEGRATION CONTRACT
Use cURL, JavaScript fetch, Python, or your existing HTTP client. The OpenAPI document describes the request surface; no proprietary SDK is required.
Reuse an idempotency key with the same body to retrieve the same logical run. Use a new key for a fresh observation.
Read the contractUse max_credits and max_results to bound the reservation. Runs report credits_reserved and credits_used; unused credits are returned.
Read the contract60 requests per minute per workspace, one active run, and at most 20 unfinished runs. Source pacing and daily limits also apply.
Read the contractSTART WITH YOUR REQUIRED FIELDS
Explore all 16 action contracts and plan your first 100 credits.
Public signup and API deployment are still being prepared.