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

Engagement linkedin post

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

Engagement linkedin post.

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

Inputs

This job has one tool, so it takes that tool’s fields. Any key you send passes through unchanged.

Name Type Required Description
commentCount integer no Number of comments to fetch (1-100)
commentPaginationToken string no Token for the next page of comments
commentStart integer no Offset of the first item to return. This endpoint pages by offset: advance start by the number of items you received. Keep requesting while hasMore is true; an empty page ends the list.
postUrlOrUrn string yes Professional post URL or URN
reactionCount integer no Number of reactions to fetch (1-100)
reactionStart integer no Offset of the first item to return. This endpoint pages by offset: advance start by the number of items you received. Keep requesting while hasMore is true; an empty page ends the list.

Providers and prices

Provider Tool Price
Fetchin fetchin-post-engagement $0.003 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-post-engagement 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.engagement","input":{"postUrlOrUrn":"<postUrlOrUrn>"},"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.engagement",
    input: {
      postUrlOrUrn: "<postUrlOrUrn>",
    },
    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.engagement",
        "input": {
            "postUrlOrUrn": "<postUrlOrUrn>",
        },
        "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.engagement. 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-post-engagement that is postUrlOrUrn.

Was this page helpful?