Building a webhook integration? Read the webhook guide for signatures, retries, event schemas, and troubleshooting.

apiProvider-backed

Search people database

POST /api/leads/search

LinkedIn people search through a connected account. Resolve location, industry, company, school, function, and seniority labels first with resolve-linkedin-search-parameters. Classic requires resolved numeric IDs for location, industry, and company filters and rejects unsupported fields. Sales Navigator and Recruiter use their own contracts.

Parameters

workspaceId

string

Optional workspace ID or slug. Required when this credential can access multiple workspaces and no workspace was configured on the client.

accountId

string

UUID of the connected LinkedIn account to search through.

paramsrequired

object

Typed API-specific LinkedIn filters. Resolve location, industry, company, school, and function IDs before search.

api

string

Which LinkedIn API surface to use. Defaults to classic.

classic | sales_nav | recruiter

cursor

string

Pagination cursor from a previous response.

limit

number

Max results (1-100, default 25).

Example

REST requestbash

curl -X POST "https://app.pipeline.help/api/leads/search" \
  -H "Authorization: Bearer $PIPELINE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"params":{}}'

Response

The operation is available, but its typed response schema has not been published yet.

HTTP errors

401: Missing or invalid API key.
403: Authenticated but not permitted for the workspace or resource.
404: The requested resource was not found.