/v1/actions/linkedin-visit-profile/run/liveVisit LinkedIn Profile visits a specific LinkedIn profile and extracts the structured data from that page in the same run. You get a registered profile visit attributed to your seat plus a normalized payload — headline, experience, current company, location — ready to push into your CRM or enrichment pipeline.
This action runs on the LinkedIn level and targets sales, recruiting, and ABM teams who use profile visits as a warm-up touch and want the extraction in the same call to save a round trip.
You pass a LinkedIn profile URL or public identifier. Edges opens the profile through your authenticated LinkedIn session, registers the visit server-side, pulls the public profile data, and returns both the visit receipt and the extracted payload. The run is live and completes in a single round trip.
Because the visit is attributed to your seat, it lands in the target's "Who viewed your profile" surface (subject to their privacy settings). Everything runs on Edges infrastructure, browser-less and paced safely against LinkedIn's guidance.
Use Visit LinkedIn Profile when a warm-up touch and an enrichment pull should happen together. It slots into the LinkedIn messaging & outreach API use case as a two-in-one primitive — the visit signals interest to the target while the payload hydrates your CRM.
It also works as the first step before a connection request, since a visible visit before an invite tends to improve acceptance rates.
visited boolean as ground truth rather than assuming success.One per call. Visit LinkedIn Profile is a per-record primitive — loop it over your target list and let Edges pace between visits.
Your own LinkedIn account. Every visit runs through the session you connected to Edges, so it shows up in your activity and in the target's profile-view surface.
Yes. A common chain is Visit LinkedIn Profile → Connect LinkedIn Profile → Message LinkedIn Profile once the invite is accepted.
Run Visit LinkedIn Profile from the Edges library, wire it into your outreach warm-up flow, or call it directly from the Edges API. Browse the full Actions library to see what to chain before and after the visit.
curl -X POST "https://api.edges.run/v1/actions/linkedin-visit-profile/run/live" \
-H "X-API-KEY: <YOUR_API_KEY>" \
-H "Content-Type: application/json" \
-d '{
"identity_ids": [
"your-identity-uuid"
],
"identity_mode": "direct",
"input": {
"linkedin_profile_url": "https://www.linkedin.com/in/example-profile",
"custom_data": "example_value"
}
}'{
"sales_navigator_profile_id": "example-123",
"linkedin_profile_id": 42
}