Skip to main content
POST
Find warm intros into an account
Give it a company and the people you want to reach there. It returns those decision makers and, for each one, your 1st-degree connections who can introduce you, with the same paths, shared experiences and relationship strength as Find connections. Use it when a deal opens from outbound or inbound: before the first meeting, you know who can vouch for you inside the account.

How it works

  1. A Sales Navigator search finds the people working at the company today who match your persona_id, or your job_titles / excluded_job_titles, and who are in your 2nd-degree network: someone you know knows them.
  2. For up to limit of them, Pipecorn looks up your warm paths, as Find connections does, using the spotlights you pick (default SHARED_CONNECTION).
  3. The result is posted to your webhook_url, decision makers with the strongest warm path first.
It runs in the background: the response only holds a request_id. Expect about a minute for 10 decision makers.

Example request

company_linkedin_id is the numeric LinkedIn company id. Get it from the linkedin_id of Enrich account if you only have a domain or a URL.

Example response

Webhook payload

  • request_id matches the one returned when you started the search, and context is the object you sent, untouched.
  • total_count is the number of matching decision makers on Sales Navigator; at most limit are looked up.
  • warm_paths has the shape of the Find connections response. When LinkedIn can’t process one decision maker, it carries an error message instead.
  • When the search fails as a whole, status is failed and error says why, e.g. an expired LinkedIn session or a LinkedIn rate limit.

Requirements

  • A connected LinkedIn account with Sales Navigator. Without it the endpoint returns 422.
  • persona_id, when given, must be one of your personas (see GET /personas).

Notes

  • Doesn’t consume credits.
  • limit defaults to 10 and goes up to 25. Each decision maker costs a few Sales Navigator lookups, so keep it small.

Rate Limits

  • 1 request per second per user, on top of your plan’s per-minute limit (see Rate Limiting).

Authorizations

X-API-KEY
string
header
required

Body

application/json
company_linkedin_id
string
required

Numeric LinkedIn company id of the account (the linkedin_id returned by POST /accounts/single_enrich). A number is accepted too.

Pattern: ^\d+$
Example:

"1441"

webhook_url
string<uri>
required

URL that receives the result as a POST once the search is done.

Example:

"https://hooks.example.com/pipecorn/warm-intros"

persona_id
string<uuid>

Optional. Id of one of your personas (see GET /personas). Its job titles, locations, industries and company sizes select the decision makers. Cannot be combined with job_titles or excluded_job_titles.

Example:

"8f2c1b7e-3a4d-4e5f-9a6b-1c2d3e4f5a6b"

job_titles
string[]

Optional. Keep only decision makers whose current title matches one of these. Use it instead of persona_id.

Example:
excluded_job_titles
string[]

Optional. Drop people whose current title matches one of these. Requires job_titles.

Example:
spotlights
enum<string>[]

Optional. Kinds of warm path to look for. SHARED_CONNECTION: your connection is connected to the target. SHARED_EXPERIENCE: they worked at the same company. SHARED_EDUCATION: same school. SHARED_GROUP: same LinkedIn group. Each kind runs one more Sales Navigator lookup. TeamLink is not supported.

Minimum array length: 1
Available options:
SHARED_CONNECTION,
SHARED_EXPERIENCE,
SHARED_EDUCATION,
SHARED_GROUP
Example:
limit
integer
default:10

Maximum number of decision makers to look up.

Required range: 1 <= x <= 25
Example:

10

context
object

Optional. Any JSON object, sent back untouched in the webhook payload (e.g. your CRM deal id).

Example:

Response

Search started. The result is posted to webhook_url.

message
object