LinkedIn post search API for your agent. One call per search.
The short answer
The short answer
LinkedIn post search API for an agent: it sends a keyword to a catalog endpoint and reads post text, author and title back. Several providers sell the call, so the agent tries the cheapest first. You pay per call, and a failed call costs nothing.
Updated
- Post text
- Author and title
- Likes and comments
- Published date
- Post link
The job
What the LinkedIn post search API gives your agent
LinkedIn posts show what people in a profession say in public. Your agent sends a keyword and reads back the posts with their authors, text and engagement. It finds the posts where a problem you solve is described, and the people who wrote them.
The two providers work differently. One searches posts directly, with filters for the author's title and industry, the content type and the date, and bills per three results. The other finds posts, feed updates and Pulse articles through Google Search, so its results depend on what Google has indexed.
You give
a keyword
data warehouse migration
You get
- Post text
- Author and title
- Likes and comments
- Published date
- Post link
Providers, cheapest first
What actually differs between providers
One of these endpoints has a live price today, $0.00188 per call. The list is ranked by price, and each entry says what that endpoint does differently.
ScrapeCreators
$0.00188 / callFinds public posts, feed updates and Pulse articles through Google Search, so results follow what Google has indexed.
scrapecreators-linkedin-search-posts- Any Site APIprice on request
Searches posts with filters for author title, author industries, content type and date, and bills per result.
anysite-api-linkedin-search-posts
Cost
What 100 LinkedIn post search runs cost
$0.1880
100 searches cost about $0.1880 through ScrapeCreators. Each run is one call.
Sample calls
The request and what comes back
Each run is one POST to /v1/runs with an endpoint id and an input. These are illustrative calls with generic values. The run's result holds the provider's own fields.
{"endpointId":"anysite-api-linkedin-search-posts","input":{"keywords":"data warehouse migration","count":10},"wait":30}// POST /v1/runs, then read run.status and run.result // result: searches posts with filters for author title, author industries, content type and date, and bills per result
The prompt
Copy one prompt, give it to your agent.
Edit the names and numbers, paste it, and the agent runs the job and shows the cost.
- One run is one search.
- 1 step across 2 providers.
- Runs on demand, whenever you ask.
set up looot for LinkedIn post search API - https://looot.ai/use-cases/linkedin-post-search-api/skill.mdBefore you start
Settle these before the first run
- Know the source. The second provider reads what Google indexed, so a very recent post may not appear yet.
- Filter by author title when you sell to a role. A search for the keyword with the title VP of Data returns posts from the people you want.
- Check LinkedIn's terms and your privacy rules before you store personal data from posts.
FAQ
Questions people ask
More ways to run this job
- use case
- LinkedIn post search API
- run
- search
- schedule
- on demand
- step
- Search LinkedIn posts: anysite scrapecreators
- setup
- https://looot.ai/use-cases/linkedin-post-search-api/skill.md
- llms.txt
- https://looot.ai/llms.txt
- updated
- 2026-10-04
Try LinkedIn post search with your own agent.
Start your workspace, top up, and paste the prompt into the agent you already use.