Skip to content
looot docs
Esc
↑↓navigate↵open⌘Jpreview
On this page

Posts linkedin person

Run job:linkedin.person.posts through the looot API: 2 providers, from $0.0015 per call. Inputs, prices, output shape and code for curl, JavaScript and Python.

Posts linkedin person.

Job id linkedin.person.posts, in Social data (LinkedIn). As of 2026-10-07, 2 providers serve it through 2 tools. Run job:linkedin.person.posts 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
paginationToken string 2 of 2 0 Cursor for the next page: pass back the paginationToken from the previous response, unchanged. Omit it to start from the beginning. A value this API did not issue is rejected with 400. Keep paging while hasMore is true.
count integer 1 of 2 0 Number of posts to fetch (default: 10)
page integer 1 of 2 0 Page number for pagination
postedLimit string 1 of 2 0 Filter posts by maximum posted date. Supported values: ‘24h’, ‘week’, ‘month’. Since LinkedIn doesn’t offer a way to filter by date, the filtering will be done on our side, due to that the pagination might have incorrect values, because pagination i
profile string 1 of 2 0 Filter posts by author’s profile URL or public identifier or profile ID.
profileUrlOrUrn string 1 of 2 1 The professional profile to fetch. Accepts a profile URN (recommended for consistency, since a profile’s public identifier can change over time while the URN does not; example urn:li:fsd_profile:ACoAAA8BYqEBCGLg_vT_ca6mMEqkpp9nVffJ3hc), a public identifier/slug (also fine; example williamhgates).
scrapePostedLimit string 1 of 2 0 Post-Filter posts by maximum posted date. Supported values: ‘1h’, ‘24h’, ‘week’,‘month’, ‘3months’, ‘6months’, ‘year’. This parameter will be applied after receiving results from LinkedIn, the filtering will be done on our side
start integer 1 of 2 0 Not supported on this endpoint. This feed is cursor-paginated and ignores offsets, so a non-zero value is rejected with 400 rather than silently returning the first page again. Page with paginationToken instead.

Providers and prices

Provider Tool Price
Fetchin fetchin-posts $0.0015 per call
HarvestAPI harvestapi-profile-posts $0.004 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 fetchin-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.person.posts","input":{"profileUrlOrUrn":"<profileUrlOrUrn>"},"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.person.posts",
    input: {
      profileUrlOrUrn: "<profileUrlOrUrn>",
    },
    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.person.posts",
        "input": {
            "profileUrlOrUrn": "<profileUrlOrUrn>",
        },
        "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.person.posts. The shared input names above are for the job: run only; a tool id takes that tool’s own field names, listed on its page, and refuses the shared ones when they differ. For fetchin-posts that is profileUrlOrUrn.

Was this page helpful?