Skip to main content
The Search Profiles endpoint creates an async task to search LinkedIn for people matching your criteria. Provide one or more search filters and receive a task ID to poll for the matching profiles.

Endpoint

Request Body

At least one filter field is required.
string
General keyword search across name, headline, and profile text
string
Filter by job title (e.g., "VP of Engineering")
string
Filter by current company name (e.g., "Google")
string
Filter by first name
string
Filter by last name
string[]
Array of LinkedIn geographic URNs to filter by location (e.g., ["103644278"] for United States)
string[]
Array of LinkedIn company URNs to filter by current employer
string[]
Array of LinkedIn industry URNs to filter by industry
string[]
Array of LinkedIn company URNs to filter by past employer
string
Filter by school or university name (e.g., "MIT")
string[]
Array of language codes to filter by profile language (e.g., ["en"])
number
Number of profiles to return. Defaults to 25, maximum 50.
You can combine multiple filters for more precise results. For example, pass both title and geo_urn to find “Software Engineers in San Francisco”. At least one filter must have a value, sending an empty body will return a 400 error.

Response

The endpoint returns immediately with a task ID. The search is executed asynchronously.
boolean
Whether the task was created successfully
string
UUID to poll for results via Get Task Status
string
Human-readable confirmation

Polling for Results

After creating the task, poll the Get Task Status endpoint until the status is completed:

Completed Response

When the task finishes, task_output contains the matching profiles:

Code Examples

Error Responses

FAQ

Each profile in the search results typically includes: full name, headline, location, profile slug, profile URN, connection degree (1st, 2nd, or 3rd+), and profile image URL. The profile slug and URN can be used with other API endpoints such as Fetch Profile and Send Message.
The count parameter is capped at 50 profiles per request. If you pass a value greater than 50, it will be clamped to 50. The default is 25 if count is not specified.
LinkedIn URNs for geography, industry, and company can be found by inspecting LinkedIn Voyager API requests in your browser’s developer tools when performing a search on LinkedIn. Common geo URNs: 103644278 (United States), 101165590 (United Kingdom), 102713980 (India).
Yes. OutX is a proxy and does not rate-limit requests on your behalf. Each search is executed as a real LinkedIn people search. Running many searches in rapid succession can trigger LinkedIn’s activity monitoring. Space requests at least 10–30 seconds apart. See Rate Limits.
Yes. Each profile in the results includes a profile_slug. You can pass that slug to the Fetch Profile endpoint to retrieve the full profile data including experience, education, and skills.

Learn More