/v1/actions/linkedin-me/run/liveMe returns the authenticated member context for the LinkedIn session currently connected to Edges — your own profile ID, public URL, name, headline, and account entitlements. You get a single-record primitive used to validate that a session is alive and to drive branching based on which account is executing a workflow.
It runs on the LinkedIn level and reads the session's own identity, nothing else.
Edges signs the request with your authenticated LinkedIn session and asks LinkedIn for the current member's basic profile and entitlement payload. No inputs are required beyond the connected account. The action runs on Edges infrastructure with safe pacing, so you do not manage cookies or retries yourself.
Because Me is cheap and read-only, it is the standard health check in multi-account workflows. Use it to confirm the session is still authenticated before spending credits on downstream sends or extractions.
Use Me at the top of every multi-step workflow that depends on a specific account, and any time your orchestration layer needs to decide which branch to run based on session state. It plugs naturally into the LinkedIn profile & company data API workflow as the session-validation primitive before enrichment or outreach.
It is also the cleanest way to enforce multi-tenant safety: run Me first, confirm the returned profileId matches the expected tenant, then proceed.
sessionStatus is not active.profileId matches what your workflow expects.inmailCreditsRemaining is below threshold.expired or restricted — fail fast and alert the operator.One per run. Me always targets the single session that executes the action — to check multiple accounts, invoke Me once per connected account.
Your LinkedIn account. The whole point of Me is to return the identity of the session you connected, so there is no shared-pool behavior.
Yes. Teams commonly chain Me before Extract LinkedIn Connections, Message LinkedIn Profile, or any credit-spending action to confirm the session is alive and the right account is about to act.
Drop Me at the top of every multi-step Edges workflow, or call it directly from the Edges API as your session health check. Browse the full Actions library to see what to chain after the preflight.
curl -X POST "https://api.edges.run/v1/actions/linkedin-me/run/live" \
-H "X-API-KEY: <YOUR_API_KEY>" \
-H "Content-Type: application/json" \
-d '{
"identity_ids": [
"your-identity-uuid"
],
"identity_mode": "direct"
}'{
"id": 42,
"first_name": "John",
"last_name": "Doe",
"full_name": "John Doe",
"job_title": "Software Engineer at Example Corp",
"object_urn": "example_value",
"handle": "example-123",
"twitter": "example_value",
"premium_subscriber": true,
"linkedin_profile_url": "https://www.linkedin.com/in/example-profile",
"profile_image_url": "https://www.linkedin.com/in/example-profile",
"sales_navigator_profile_id": "example-123"
}