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

Search linkedin person

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

Search linkedin person.

Job id linkedin.person.search, in Social data (LinkedIn). As of 2026-10-07, 1 provider serve it through 1 tool. Run job:linkedin.person.search 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
currentCompany string no Filter by company ID or Company URL. One value or multiple comma-separated
firstName string no Filter by first name
followerOf string no Filter profiles that are followers of a LinkedIn profile. Provide the profile URL or ID. One value or multiple comma-separated
geoId string no Filter by location as LinkedIn Geo ID. Overrides the location query param. Use the /linkedin/geo-id-search endpoint to find the Geo ID
industryId string no Filter by industry ID. One value or multiple comma-separated
keywordsCompany string no Filter by keywords in company name
keywordsSchool string no Filter by keywords in school name
lastName string no Filter by last name
location string no Filter by location text
page string no Page number, use for pagination
pastCompany string no Filter by past company ID or Company URL. One value or multiple comma-separated
school string no Filter by school ID or School URL. One value or multiple comma-separated
search string no Search profiles by name
title string no Filter by title

Providers and prices

Provider Tool Price
HarvestAPI harvestapi-profile-search $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 harvestapi-profile-search 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.search","input":{"page":"<page>"},"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.search",
    input: {
      page: "<page>",
    },
    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.search",
        "input": {
            "page": "<page>",
        },
        "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.search. 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.

Was this page helpful?