Fetchin / Posts a person reacted to
Fetchin tool fetchin-profile-reactions on looot: input fields, $0.0015 per call, output shape, and code to run it with curl, JavaScript or Python.
Fetch posts that a professional profile has reacted to (liked, loved, etc.) with the reaction type and full post details. The post object in each reaction has the same shape as items returned by GET /api/v1/posts.
- Tool id:
fetchin-profile-reactions - Provider: Fetchin
- Job: Reactions linkedin person (
linkedin.person.reactions) - Price: $0.0015 per call. A call that fails at the provider costs $0.
Inputs
| Name | Type | Required | Description |
|---|---|---|---|
count |
integer | no | Number of reactions to fetch (default: 10) |
paginationToken |
string | no | 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. |
profileUrlOrUrn |
string | yes | 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 | no | 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. |
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":"fetchin-profile-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: "fetchin-profile-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": "fetchin-profile-reactions",
"input": {
"profileUrlOrUrn": "<profileUrlOrUrn>",
},
"wait": 30,
},
timeout=90,
)
run = response.json()
print(run["status"], run.get("result"))To let looot pick among every provider of this job instead, send job:linkedin.person.reactions as endpointId; see the job page.