Skip to main content
POST
Search database leads

Use Case:

Search cached lead data with fast database filters.

Pricing

Full rows are billed: you are charged for each result returned. If no results are found, the request is free. A request without limit_by returns at most 100 rows, so that is the most it is billed for. data.results_count is the whole match; page through the rest with offset_by.

Free thin rows

Send "detail": "thin" and the same search returns thin rows at no charge. A thin row tells you who the person is, their role, where they are and which company they work at: id, first_name, last_name, full_name, job_title, seniority, location_name, location_country, location_city, company_name, linkedin_company_id, company_industry, company_location_country and updated_at. It has no LinkedIn profile URL, no company domain or website, no contacts and no work history. Keep the ids that fit and pay only for what you take further (enrich, find an email or a phone).
  • Thin rows are free up to a daily quota per account, currently 2,000 rows per UTC day. meta.free_tier on every thin response reports daily_rows, rows_used_today and rows_left_today, and a page is cut to the rows you have left today.
  • When the day’s rows are used up, a thin search returns 429 with a Retry-After header until 00:00 UTC. It is never billed instead: "detail": "full" keeps working, billed per row.
  • meta.amount_charged is 0 on every thin response, and a thin search works on a zero balance.
  • Leaving detail out, or sending "detail": "full", returns full rows billed per row exactly as before. Existing integrations are unaffected.
  • Accounts on a custom API contract are priced by their contract, so a thin search there returns 400 unless the contract includes it.
  • The Generect MCP asks for thin rows by default.
Your price decreases automatically as your lifetime spend grows. Check your current tier and pricing →

Authorizations

Authorization
string
header
required

Use the required Token prefix. Example: Authorization: Token xxxxxxxxx

Body

application/json
job_titles
string[]

Job titles held by the people you want to find. A lead only needs to match one of the titles you provide — adding more expands your search. Results may also include similar titles (e.g. "marketing manager" can return "content marketing manager"). Combine with seniorities to target both function and level. Examples: "sales development representative", "marketing manager", "software engineer".

seniorities
string[]

Job seniority levels at the lead's current employer (current position only, not previous roles). A lead needs to match at least one; adding more values expands your search. Allowed values: owner, founder, c_suite, partner, vp, head, director, manager, senior, entry, intern. Combine with job_titles to narrow targeting.

locations
string[]

Geographic locations where leads currently live — matches across cities, states/regions and countries. A lead needs to match at least one. To filter by the employer's HQ location, use company_locations. Examples: "San Francisco, California, United States", "Germany", "London".

exclude_locations
string[]

Locations to exclude from results.

company_locations
string[]

Headquarters location of the lead's current employer; a lead is included if their company's HQ matches at least one. Filters by where the company is based — distinct from locations, which is where the lead personally lives.

exclude_company_locations
string[]

Company locations to exclude.

company_industries
string[]

Industries of the lead's current employer; a lead is included if their company matches at least one. Values follow LinkedIn's industry taxonomy. Examples: "Software Development", "Financial Services", "Information Technology".

exclude_company_industries
string[]

Company industries to exclude.

company_headcounts
string[]

Size of the lead's current employer, as employee-count ranges; a lead is included if their company falls into at least one. Allowed values: "1-10", "11-50", "51-200", "201-500", "501-1000", "1001-5000", "5001-10000", "10 000+".

exclude_company_headcounts
string[]

Company size ranges to exclude.

company_types
string[]

Company types: "Public Company", "Privately Held", "Non Profit", "Government Agency", "Educational", "Self Employed", "Partnership", "Self Owned".

company_name
string

Target company name (mutually exclusive with company_link and company_id).

LinkedIn company URL (mutually exclusive with company_name and company_id).

company_id
integer

LinkedIn company numeric ID (mutually exclusive with company_name and company_link).

exclude_names
string[]

Skip leads by full name.

exclude_ids
string[]

Skip leads by Sales Navigator ID.

filter_empty_vars
string[]

Skip leads where these fields are empty. Options: job_started_on, profile_photo, started_at_position, company_website.

limit_by
integer
default:100

Maximum number of leads to return. Without it, a search returns 100 rows: results_count is the whole match, and offset_by reaches the rest. For filter-only searches (no company_id/company_link/company_name) the maximum is 2400.

offset_by
integer

Number of leads to skip (for pagination). For filter-only searches the maximum is 2399.

strict
string[]

Fields to apply strict matching on (e.g. "company_locations").

skip_truncated_names
boolean
default:false

Drop leads whose first or last name is a single character or empty. LinkedIn abbreviates surnames for members who restrict their profile, so these rows carry a name that cannot be personalised. Applies to both database and realtime search.

detail
enum<string>
default:full

Row shape. full (the default) returns full rows, billed per row. thin returns who, what role, where and which company at no charge, up to a daily quota per account (currently 2,000 rows per UTC day); a thin row has no LinkedIn profile URL, company domain, contacts or work history. A spent quota is refused with 429 until 00:00 UTC, never billed. Accounts on a custom API contract get 400 unless their contract includes thin search. The count endpoints ignore this field: counts are always free.

Available options:
full,
thin
gender
enum<string>[]

Gender of the lead; a lead is included if it matches at least one value. Case-insensitive; any other value is rejected with 400. Gender is inferred from the lead's name, so it is an estimate, and a lead whose name does not point to one is unknown. To leave a gender out, list the others — e.g. ["female", "unknown"].

Database mode only. LinkedIn search has no gender facet, so realtime search rejects this field rather than accepting it and returning a wider result set than you asked for.

Coverage matters here: gender is known for roughly a third of leads, and the rest are unknown. Filtering by male or female therefore also drops leads whose gender simply is not known, not only those of the other gender.

Available options:
male,
female,
unknown
Example:
seniority_levels
enum<string>[]

Seniority level of the lead's current role, as our model reads it from the lead's job title and profile summary. A lead is included if it matches at least one level. Case-insensitive; any other value is rejected with 400, and the error lists the levels. To leave a level out, list the others.

Not the same as seniorities, which matches words in the job title (vp, director, …). Each lead has one level, so a level finds every title that means it without listing the titles. About 1% of leads have no level yet; a seniority_levels filter leaves them out.

Database mode only. LinkedIn search has no such field, so realtime search rejects it rather than returning a wider result set than you asked for.

Available options:
In Training,
Entry Level,
Senior,
Entry Level Manager,
Experienced Manager,
Director,
Vice President,
Strategic,
Owner & Partner,
CXO
Example:
exact_locations
string[]

Locations matched against the lead's whole location, not anything inside it. "California, United States" here finds leads whose location is the state alone, with no city, while in locations it finds every city of the state as well. LinkedIn metro areas ("San Francisco Bay Area", "Los Angeles Metropolitan Area") are locations of their own and are not included.

Combined with locations by OR: locations: ["Los Angeles, California, United States"] with exact_locations: ["California, United States"] returns leads in Los Angeles and leads who give only California, and no other city of the state. Takes the same names as locations; an unknown name is rejected with 400.

Database mode only. LinkedIn search cannot leave out the cities of a state, so realtime search rejects this field rather than returning the whole state.

Example:

Response

Lead search results

data
object

Search results.

meta
object

Operation metadata returned in every data/meta response.