Search linkedin post

Run job:linkedin.post.search through the looot API: 1 provider, from $0.002 per call. Inputs, prices, output shape and code for curl, JavaScript and Python.

Search linkedin post.

Job id linkedin.post.search, in Social data (LinkedIn). As of 2026-10-01, 1 provider serve it through 2 tools. Run job:linkedin.post.search and looot picks one of them; with fallback on, a miss moves on to the next. See Jobs.

Inputs

Fields the job’s tools take, most shared first. Any key you send passes through unchanged.

Name	Type	Taken by	Required by	Description
`datePosted`	string	2 of 2	0	Filter by recency. One of last-hour, last-day, last-week, last-month, last-year.
`query`	string	2 of 2	2	The post search query.
`authorCompanyNames`	array	1 of 2	0	Only return posts by people associated with these company names.
`authorIndustryIds`	array	1 of 2	0	Only return posts by authors associated with these LinkedIn industry IDs.
`authorKeywords`	string	1 of 2	0	Only return posts whose author profile headline or job title contains at least one of these keywords.
`authorUrls`	array	1 of 2	0	Only return posts authored by these LinkedIn profile or company URLs.
`contentType`	string	1 of 2	0	Only return posts carrying this content type.
`cursor`	string	1 of 2	0	Pagination cursor from a previous response.
`limit`	integer	1 of 2	0	Maximum number of posts to return (1-100, default 10). The upper bound is one LinkedIn search page.
`mentioningMemberUrls`	array	1 of 2	0	Only return posts mentioning these LinkedIn member profile URLs.
`sort`	string	1 of 2	0	Order results by search relevance or publication date.

Providers and prices

Provider	Tool	Price
AnyAPI	`anyapi-run-linkedin-search-posts`	$0.002 per call
AnyAPI	`anyapi-run-linkedin-search-posts-full`	$0.0143 per call

A call that fails at the provider costs $0. See What’s free.

Output

The run’s result holds the provider’s answer. Signed in, looot inspect anyapi-run-linkedin-search-posts prints its fields.

Run it

Every call needs your API token in LOOOT_TOKEN; Sign in shows how to get one. Each run also needs a new idempotency key, so a retry never pays twice. With wait: 30 the answer comes back inline when the run ends within 30 seconds. Otherwise you get the running run back: poll GET /v1/runs/<runId>.

Example input with placeholder values:

curl -X POST "https://api.looot.ai/v1/runs" \
  -H "Authorization: Bearer $LOOOT_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"endpointId":"job:linkedin.post.search","input":{"query":"<query>"},"wait":30}'

const response = await fetch("https://api.looot.ai/v1/runs", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.LOOOT_TOKEN}`,
    "Content-Type": "application/json",
    "Idempotency-Key": crypto.randomUUID(),
  },
  body: JSON.stringify({
    endpointId: "job:linkedin.post.search",
    input: {
      query: "<query>",
    },
    wait: 30,
  }),
});
const run = await response.json();
console.log(run.status, run.result);

import os
import uuid

import requests

response = requests.post(
    "https://api.looot.ai/v1/runs",
    headers={
        "Authorization": f"Bearer {os.environ['LOOOT_TOKEN']}",
        "Idempotency-Key": str(uuid.uuid4()),
    },
    json={
        "endpointId": "job:linkedin.post.search",
        "input": {
            "query": "<query>",
        },
        "wait": 30,
    },
    timeout=90,
)
run = response.json()
print(run["status"], run.get("result"))

To pin one provider, send its tool id as endpointId instead of job:linkedin.post.search.