/v1/actions/linkedin-search-content/run/liveSearch LinkedIn Content extracts posts data from a LinkedIn content search so you can monitor topics, surface intent signals, and build content intelligence feeds. You get each matching post as a structured row — author, text, engagement counts, URL — ready to route into your analytics, alerting, or outreach stack. It targets growth, marketing, and RevOps teams that treat LinkedIn activity as a signal source.
The action runs on the LinkedIn level and uses your authenticated LinkedIn session on Edges.
You pass a LinkedIn content search URL or a keyword plus filters (date posted, author type, language), and Search LinkedIn Content iterates the search result pages on your behalf. Edges walks pagination, normalizes each post, and returns an array of post objects with stable fields.
Every request runs through your authenticated LinkedIn session and is paced to respect activity guidance. The action supports async execution, which is the right mode for any multi-page search.
Reach for Search LinkedIn Content whenever posts themselves are the signal. Tracking mentions of your product, watching competitor announcements, finding buyers who talk about a pain point — all start from a content search and need the posts as structured data.
It plugs into the LinkedIn signals and intent API use case. Teams wire it into alerting and outreach flows so a post becomes a work item within minutes of publishing.
postId as your primary key to avoid reprocessing.As many as LinkedIn paginates for your search. Specific keywords with a tight date window typically return the full set; very broad queries will hit LinkedIn's pagination ceiling.
Your LinkedIn account. Every search is executed through the LinkedIn session you connect to Edges, so the posts returned match what your account would see manually.
Yes. Pass each postUrl into Extract LinkedIn Post for the full post payload, then into Extract LinkedIn Post Commenters or Like LinkedIn Post for downstream engagement.
Run Search LinkedIn Content from the Edges library, schedule it on a keyword list, or call it directly from the Edges API. Browse the full Actions library to see the extraction and engagement actions that pair with it.
curl -X POST "https://api.edges.run/v1/actions/linkedin-search-content/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_content_search_url": "https://www.linkedin.com/in/example-profile",
"custom_data": "example_value"
},
"parameters": {
"only_extract_unique_profile": true
}
}'[
{
"author_name": "Example Name",
"content_text": "example_value",
"headline": "Software Engineer at Example Corp",
"linkedin_post_url": "https://www.linkedin.com/in/example-profile",
"linkedin_post_id": "example-123",
"linkedin_profile_url": "https://www.linkedin.com/in/example-profile",
"comment_count": 42,
"reaction_count": 42,
"repost_count": 42,
"published_time": "example_value",
"published_date": "1990-01-01",
"profile_image_url": "https://www.linkedin.com/in/example-profile",
"linkedin_profile_handle": "example-123",
"content_image_url": "https://www.linkedin.com/in/example-profile",
"linkedin_job_url": "https://www.linkedin.com/in/example-profile",
"linkedin_profile_id": 42,
"linkedin_company_id": 42,
"linkedin_company_url": "https://www.linkedin.com/in/example-profile"
}
]