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

Reactions linkedin person

Run job:linkedin.person.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 person.

Job id linkedin.person.reactions, in Social data (LinkedIn). As of 2026-10-07, 2 providers serve it through 2 tools. Run job:linkedin.person.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
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 reactions to fetch (default: 10)
page integer 1 of 2 0 Page number for pagination. Default is 1
profile string 1 of 2 0 URL of the LinkedIn profile 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).
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-profile-reactions $0.0015 per call
HarvestAPI harvestapi-profile-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-profile-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.person.reactions","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.reactions",
    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.reactions",
        "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.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-profile-reactions that is profileUrlOrUrn.

Was this page helpful?