Check when a LinkedIn member was last active
Find when a LinkedIn member last showed public activity, such as a post, with an exact timestamp, by profile URL. 50 credits per call.
To check when a LinkedIn member was last active, call GET /v1/linkedin/profile/activity with their profile url. It returns the time of their most recent public activity, what kind of activity it was (for example post), and LinkedIn's short "how long ago" label such as 2w. It costs 50 credits a call. It answers "is this person still active on LinkedIn?" without pulling their whole feed.
Cost
50 credits per call. Checking 100 profiles costs 5,000 credits. Asking for the same profile again within 24 hours is answered from the shared cache for 2 credits. Failed calls and empty results are free.
How do I find the profile URL?
Use the member's public profile address, the one in the browser bar on their profile: https://www.linkedin.com/in/adamselipsky/. If you have a name but no URL, GET /v1/linkedin/search/people finds members by keyword, and every person row other endpoints return carries the profile link in author.url.
Make the request
curl -G "https://api.insightsocial.app/v1/linkedin/profile/activity" \
--data-urlencode "url=https://www.linkedin.com/in/adamselipsky/" \
-H "x-api-key: $INSIGHTSOCIAL_API_KEY"What comes back
A real response from 2026-10-14, complete apart from the billing fields at the end.
{
"success": true,
"endpoint": "/v1/linkedin/profile/activity",
"schema_version": "2",
"data": {
"date": "2026-09-29 00:28:48.785 +0000 UTC",
"recent_activity": "2w",
"timestamp": "2026-09-29T00:28:48.785Z",
"type": "post"
},
"unavailable": [],
"credits_used": 50
}| Field | What it holds |
|---|---|
data.timestamp | When the most recent public activity happened, as an ISO 8601 UTC time. Use this one for date math. |
data.date | The same moment as a plain text string. |
data.type | What the activity was. Here post: the member's latest public activity was a post. |
data.recent_activity | LinkedIn's relative label for how long ago it was. 2w here: two weeks before the call, which matches the timestamp (15 days). |
What are the limits?
- Public activity, not logins. The endpoint reports the latest activity LinkedIn shows publicly, such as a post. It does not tell you when someone last logged in, read their feed or viewed a profile. A member who reads LinkedIn daily but never posts can look inactive.
- One event, not a feed. You get the time and type of the latest activity only, not its content. Use
GET /v1/linkedin/profile/postsfor the posts themselves. - Coarse label.
recent_activityis a rounded label like2w. Compute recency fromtimestampif you need days. - Cached for up to 24 hours. A call inside that window can be answered from the shared cache, so very recent activity may not show yet. Add
fresh=1to skip the cache and pay the full 50 credits. See Caching.
What can I build with it?
- Lead list hygiene. Before outreach, check each prospect and drop or deprioritize the ones with no public activity in months. A post this month means a message is more likely to be seen.
- Engagement timing. Contact people shortly after they post, while they are checking their notifications.
- Account monitoring. Track the last-active date of a competitor's executives or key customers' champions across weeks to notice who has gone quiet.
Related
GET /v1/linkedin/profile/activityreference: every parameter and field.GET /v1/linkedin/profile/posts: the member's posts, once you know they are active.GET /v1/linkedin/profile: their name, headline, location and follower count.- LinkedIn endpoints: everything the API covers on LinkedIn.
Get the people who reacted to or reposted a LinkedIn post
List who reacted to a LinkedIn post, with each reaction type, and who reposted it, by post URL. 100 credits a page of reactors, 50 a page of reposts.
Get the posts in a LinkedIn group
Read a LinkedIn group's discussion feed: post text, author, headline, likes, comments, shares and publish time, by group ID. 50 credits per page.