Use case, LinkedIn post search

LinkedIn post search API for your agent. One call per search.

Send a keyword. Read post text and author back. Your agent picks the provider, and you pay per call.

Give this to your agent
set up looot - https://looot.ai/skill.md

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

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.

Request
{"endpointId":"anysite-api-linkedin-search-posts","input":{"keywords":"data warehouse migration","count":10},"wait":30}
ResponseSample output
// 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 steps across 2 providers.
  • Runs on demand, whenever you ask.
Prompt: LinkedIn post search API
Use looot to search public LinkedIn posts about data warehouse migration and return the author, text, likes, comments and date of each, newest first. 1. Set up https://looot.ai/skill.md. 2. Search the catalog for each step and check its price before you call. 3. Run the cheapest endpoint that fits. 4. Show the results as a table and the total cost.

Give this to your agent
Setup command
set up looot - https://looot.ai/skill.md

Before 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

Find the people who describe a problem you solve, then look up their profile and work email. Or collect the phrases buyers use and reuse them in your copy. Your agent keeps the post link as the source.

For agents
use case
LinkedIn post search API
run
search
schedule
on demand
step
Search LinkedIn posts: anysite scrapecreators
setup
https://looot.ai/skill.md
llms.txt
https://looot.ai/llms.txt
updated
2026-10-04
markdown /use-cases/linkedin-post-search-api.md

Try LinkedIn post search with your own agent.

Start your workspace, top up, and paste the prompt into the agent you already use.

Start your workspace See agent recipes