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 for LinkedIn post search API - https://looot.ai/use-cases/linkedin-post-search-api/skill.md

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.

  1. ScrapeCreators logoScrapeCreators

    Finds public posts, feed updates and Pulse articles through Google Search, so results follow what Google has indexed.

    scrapecreators-linkedin-search-posts
    $0.00188 / call
  2. Any Site API

    Searches posts with filters for author title, author industries, content type and date, and bills per result.

    anysite-api-linkedin-search-posts
    price on request

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.

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 step 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 for LinkedIn post search API - https://looot.ai/use-cases/linkedin-post-search-api/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.

The direct provider bills per result, so set a count. The Google-based one returns a page of results with a cursor. Your agent pages until it has the number you asked for.

Send the keyword to a LinkedIn post-search endpoint. Your agent reads back the posts with their authors, text and engagement.

Yes, on the provider that has an author-title filter. It also filters by the author's industry, the content type and the date.

The Google-based provider returns Pulse articles along with posts and feed updates.

That depends on how you collect and use the data and where you operate. looot returns data from providers and does not give legal advice. Check LinkedIn's terms and your privacy rules.

You pay per call, and the price depends on the provider your agent picks. This page reads the cheapest live price from the catalog and shows no number when the catalog is unreachable.

No. A call that fails at the provider costs nothing, and your agent can retry it or send it to another provider.

No. One looot key reaches every provider in the catalog. You top up once, and each call is billed at the price shown before it runs.

Send a POST to /v1/runs with the endpoint id, the input and a new idempotency key, and your looot token in the Authorization header. With wait set to 30, the answer comes back in the response when the run ends within 30 seconds. Otherwise poll GET /v1/runs/<runId>.

That needs scheduled runs, not available yet. Run it by hand whenever you want fresh results.

No. looot bills per call, and nothing runs while your agent is idle.

More ways to run this job

For agents
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.