Reactions linkedin post
Run job:linkedin.post.reactions through the looot API: 2 providers, from $0.0015 per call. Inputs, prices, output shape and code for curl, JavaScript and Python.
Reactions linkedin post.
Job id linkedin.post.reactions, in Social data (LinkedIn). As of 2026-10-07, 2 providers serve it through 2 tools. Run job:linkedin.post.reactions 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 |
|---|---|---|---|---|
count |
integer | 1 of 2 | 0 | Number of reactions to fetch (default: 100) |
page |
integer | 1 of 2 | 0 | Page number for pagination. Default is 1 |
post |
string | 1 of 2 | 0 | URL of the LinkedIn post (required) |
postUrlOrUrn |
string | 1 of 2 | 1 | Professional post URL or URN. Example: “https://www.linkedin.com/posts/username_post-slug-1234567890-abcd” |
sortBy |
string | 1 of 2 | 0 | Sort comments by field. Supported values: ‘relevance’, ‘date’ |
start |
integer | 1 of 2 | 0 | 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-reactions |
$0.0015 per call |
| HarvestAPI | harvestapi-post-reactions |
$0.02 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-reactions 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.reactions","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.reactions",
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.reactions",
"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.reactions. 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-reactions that is postUrlOrUrn.