Data catalog / search

Search data

Search across LinkedIn profiles by account filters (industry, domain, company) and contact filters (job title, location).

Last updated September 23, 2026

How it works

Filter across 700M+ LinkedIn profiles by account attributes (industry, domain, company size) and contact attributes (job title, location) at once. Billing is per result returned, not per call, so a narrow, well-targeted filter costs less than a broad one.

When to use it

Use this for broad discovery — "founders at 50-200 person software companies" — then narrow further with lead_search once you know exactly who you're after, or pipe results straight into enrich_profile for full detail.

Reference

accountobject · Optional
Account filters — linkedin, domain, industry, employeeSize.
contactobject · Optional
Contact filters — jobTitle, location.
pageinteger · Required
Page number (zero-based).
sizeinteger · Required
Results per page, 1-100. Defaults to 10.

Request

Minimum required parameters for a search data call.

Request
{
  "account": { "industry": ["software development"] },
  "contact": { "jobTitle": ["founder"], "location": ["united states"] },
  "page": 0,
  "size": 10
}

See it in a workflow

Playbooks

Real patterns, recipes, and prompts other builders run on RichAPI

Start free with 25 credits

Developer Docs

Auth, request shape, and error handling

See Documentation

FAQ

Frequently asked questions

Search across LinkedIn profiles by account filters (industry, domain, company) and contact filters (job title, location).
Every endpoint is billed from the same credit pool, at the published rate on /pricing — never a separate contract per endpoint.
Yes — the same endpoint is reachable from an MCP client (Claude, ChatGPT, Cursor, Windsurf) using the same key and credit pool. See /mcp.

Related data