People Search API for Fast, Accurate Prospecting

Find decision-makers by LinkedIn URLs or filters and keep searches organized in your dashboard, with clear pagination and production-ready rate limits.

Grab API Key

Benefits that Make People Search Usable

Stop guessing and start targeting. Redrob turns people's search into usable lists with LinkedIn inputs, crisp filters, and results you can actually operationalize.

Find People from LinkedIn Inputs

Search by a single LinkedIn URL or send LinkedIn URLs in bulk to power faster prospect search API flows.

Build Targeted Lists with Filters

Create lead search API lists using fields like job title, seniority, skills, location, company, and industry.

Keep Searches Organized in the Dashboard

All People Search API runs are visible on your dashboard. Use a readable title to find searches later.

Scale Within Clear Limits

Designed for teams running a B2B prospecting API in production with defined per-minute call limits.

Want to find
your next buyers?

Use the People Search API as a decision maker search API built for prospecting workflows.

Get started

How the People Search API works

Choose your path - look up known profiles via LinkedIn URLs or discover new prospects with filters. Redrob returns structured results with navigation-ready pagination.

Search by LinkedIn URLs

Send multiple LinkedIn profile URLs in one request for faster list-building.

Search by LinkedIn URL

People Search by Filters

{
  "title": "Search John Doe",
  "linkedinUrls": ["https://www.linkedin.com/in/john-doe"]
}

How the People Search API works

Choose your path - look up known profiles via LinkedIn URLs or discover new prospects with filters. Redrob returns structured results with navigation-ready pagination.

Search by LinkedIn URLs

Send multiple LinkedIn profile URLs in one request for faster list-building.

Search by LinkedIn URL

People Search by Filters

{
  "title": "Search John Doe",
  "linkedinUrls": ["https://www.linkedin.com/in/john-doe"]
}

How the People Search API works

Choose your path - look up known profiles via LinkedIn URLs or discover new prospects with filters. Redrob returns structured results with navigation-ready pagination.

Search by LinkedIn URLs

Send multiple LinkedIn profile URLs in one request for faster list-building.

Search by LinkedIn URL

People Search by Filters

{
  "title": "Search John Doe",
  "linkedinUrls": ["https://www.linkedin.com/in/john-doe"]
}

People Search Endpoints & Fields

Here’s the exact Redrob People Search API structure - Bearer auth, request fields for LinkedIn and filter searches, rate limits, and response metadata for pagination.

Use a Bearer authentication header:

Header: Authorization: Bearer <token>
<token> is your auth token.

Search People by LinkedIn URLs

Practical tip:
Use a readable title for each search. Example: Firstname Lastname

Practical tip: Use a readable title for each search. Example: Firstnamereadable

Rate limit (shown):

25 API calls per minute
Up to 100 contacts in one bulk, enabling up to 2,500 contacts per minute

Body (application/json):

title (string, required) — Example: "Search John Doe"
linkedinUrls(string[], required)

{
  "title": "Search John Doe",
  "linkedinUrls": ["https://www.linkedin.com/in/john-doe"]
}

// response
name (string, required) — Example: "success"
message (object[], required) — Example: "Success message"
error (boolean) — Example: false
data (object) with tbd (string) — Example: "67190b1b0000000000000000"

Search People by LinkedIn URL

Body (application/json):

title (string, required) — Example: "Search John Doe"
linkedinUrls(string[], required)

Rate limit (shown in interface):

30 API calls per minute

{
  "title": "Search John Doe",
  "linkedinUrl": "https://www.linkedin.com/in/john-doe"
}

People Search by Filters

Rate limit (shown):

25 API calls per minute

Body (application/json):

title (string, required) - Example: "Search John Doe"
name (string[]) - Example: "John Doe"
job_title (string[]) - Example: "Software Engineer"
seniority (string[]) - Example: "Senior"
skills (string[]) - Example: "React"
degree (string[]) - Example: "Master of Business Administration"
institution (string[]) - Example: "Harvard University"
location (string[]) - Example: "New York, NY"
company (string[]) - Example: "Google"
industry (string[]) - Example: "Technology"
min_years_of_experience (number) - Example: 1
max_years_of_experience (number) - Example: 10
is_decision_maker (boolean) - Example: false
page (number, required, default: 1) - Example: 2

{
  "title": "Search John Doe",
  "job_title": ["Software Engineer"],
  "seniority": ["Senior"],
  "skills": ["React"],
  "location": ["New York, NY"],
  "industry": ["Technology"],
  "min_years_of_experience": 1,
  "max_years_of_experience": 10,
  "is_decision_maker": false,
  "page": 2
}

// response
message (string) - Example: "Success"
metadata (object)
currentPage (number) - Example: 1
hasNext (boolean) - Example: true
lastPage (number)
nextPage (number) - Example: 2
perPage (number) - Example: 10
prevPage (number) - Example: 1
total (number) - Example: 100
people (object[])
status (string) - Example: "failed"
error (boolean) - Example: true
errors (object[])
code (string) - Example: "DATA-EMPTY"
message (string) - Example: "The data is empty"