# People search API: find contacts by title, company and location

> Search for people by job title, company, seniority and location, list everyone at a company, or describe who you want in plain English.

Source: https://www.b2benrich.com/guides/people-search-api  
Author: Dag Holmen, B2Benrich · Updated 2026-10-28

A people search API finds B2B contacts from what you know about them: their job title, the company they work at, their seniority or where they're based. You send a query, and you get back person records with names, titles, LinkedIn URLs, locations and company details.

B2Benrich has several people search endpoints because the questions are different. Listing the marketing team at one company is not the same job as finding every VP of Sales at mid-size software companies. This guide covers each endpoint, when to use it and how to page through the results.

## Pick the endpoint by what you already have

| You have | You want | Endpoint |
|---|---|---|
| A company domain, LinkedIn URL or ID | People at that company, optionally filtered | `/v1/search/company-employees` |
| A company name and a job title | People with that title there | `/v1/search/title-company` |
| A first name, last name and company domain | That one person | `/v1/search/first-last-domain` |
| A description of a role and a type of company | People across many companies | `/v1/search/prospector` |
| A sentence | Matches, plus the filters behind them | `/v1/search/ai` |

All of them are POST requests with a JSON body and your key in the `X-Api-Key` header.

## Find employees of a company

`/v1/search/company-employees` is the endpoint for account-based work. You identify the company by `domain`, `linkedin_url` or `id`, and narrow the results with these filters:

- `first_name`, `last_name`
- `job_title`, `job_function`, `job_level`, `persona`
- `city`, `state_name`, `country_name`

```bash
curl --request POST \
  --url https://api.b2benrich.com/v1/search/company-employees \
  --header 'Content-Type: application/json' \
  --header 'X-Api-Key: YOUR_API_KEY' \
  --data '{
    "domain": "acme.com",
    "job_function": "Marketing",
    "page": 1,
    "page_size": 50
  }'
```

Each record has `id`, `full_name`, `first_name`, `last_name`, `linkedin_url`, `job_title`, `company_name`, `company_domain`, `company_id` and location fields. For larger companies, page through. This Python loop pulls marketing people from a list of account domains and stops on each account when a page comes back short:

```python
import os, json, requests

BASE = "https://api.b2benrich.com"
HEADERS = {"X-Api-Key": os.environ["B2BENRICH_KEY"]}
PAGE_SIZE = 50

def employees(domain, **filters):
    page = 1
    while True:
        body = {"domain": domain, "page": page, "page_size": PAGE_SIZE, **filters}
        r = requests.post(f"{BASE}/v1/search/company-employees", json=body, headers=HEADERS)
        r.raise_for_status()
        records = r.json()["records"]
        yield from records
        if len(records) < PAGE_SIZE:
            break
        page += 1

seen = set()
with open("people.jsonl", "w") as f:
    for domain in ["acme.com", "globex.com"]:
        for p in employees(domain, job_function="Marketing", job_level="Director"):
            if p["id"] not in seen:
                seen.add(p["id"])
                f.write(json.dumps(p) + "\n")
```

Use this when you already picked the accounts. You get the whole relevant team, not just one name, which is what you want when several people weigh in on a purchase.

## Search by job title at a named company

`/v1/search/title-company` takes a `job_title` and a `company_name`. It's handy when your input is a spreadsheet with company names but no domains, or when you just need "the Head of RevOps at Acme" and nothing else.

```bash
curl --request POST \
  --url https://api.b2benrich.com/v1/search/title-company \
  --header 'Content-Type: application/json' \
  --header 'X-Api-Key: YOUR_API_KEY' \
  --data '{ "job_title": "Head of Revenue Operations", "company_name": "Acme" }'
```

If you have the domain, prefer company-employees with a `job_title` or `job_function` filter. Domains are less ambiguous than names.

## Find one specific person

When you know who you're looking for, `/v1/search/first-last-domain` finds the contact from a first name, last name and company domain. It's the lookup to run on event attendee lists, form fills or a list a colleague pasted into Slack. Once you have the LinkedIn URL, the [people enrichment API](https://www.b2benrich.com/guides/people-enrichment-api) returns the full profile.

## Search across companies

If you don't have a company list yet and want "VPs of Marketing at software companies with 201 to 500 employees", that's a Prospector query. It combines contact filters and company filters in one request and has a count endpoint, `/v1/search/prospector/count`, so you can size the list first. The [prospecting API guide](https://www.b2benrich.com/guides/prospecting-api) covers it end to end.

## Describe it in plain English

`/v1/search/ai` takes a sentence:

```json
{ "query": "Heads of RevOps at fintech companies in the UK" }
```

It returns matching records and the `prospector_search` it built from your words. Read that object to check how your sentence was interpreted, then reuse it in a Prospector request when you want repeatable, paged results. It also suits AI agents, which can pass a user's request through without building filters themselves.

## Job title search tips

Titles are the messiest field in B2B data, so:

- **Search by level and function first.** `job_level: "VP"` with `job_function: "Sales"` catches title variants you'd never list by hand.
- **Get exact values from the meta endpoint.** `/v1/search/meta/job_title`, `/v1/search/meta/job_level`, `/v1/search/meta/job_function` and `/v1/search/meta/persona` return every allowed value, paged with `has_more`.
- **Dedupe on `id`.** The same person can show up in more than one query. Their ID is the stable key.
- **Rerun on a schedule.** People change jobs. A weekly rerun of the same search, diffed on `id`, shows who's new on an account.

Since B2Benrich is unlimited API usage for $500 a month with no credits, rerunning a search or pulling a whole department doesn't cost more than pulling one name.

## From a search result to outreach

Search records don't include email addresses. Take `first_name`, `last_name` and `company_domain` from each record and call the email finder, covered in the [email finder API guide](https://www.b2benrich.com/guides/email-finder-api). Then dedupe against your CRM and load the new contacts.

## Frequently asked questions

### What is a people search API?

A people search API finds professional contacts from criteria like job title, company, seniority, function and location, and returns them as structured records. You call it from code to build contact lists or look up people at target accounts.

### How do I find all employees of a company with an API?

Call /v1/search/company-employees with the company’s domain, LinkedIn URL or ID. Add filters such as job_function or job_level to narrow it down, and page through the results with page and page_size.

### How do I search for people by job title?

Use job_title on the company-employees or Prospector endpoints, or /v1/search/title-company with a company name. Because titles vary, combining job_level and job_function usually finds more of the right people than an exact title.

### Can I search LinkedIn profiles with an API?

You search B2Benrich’s own people records with structured filters, not LinkedIn search URLs. Each record includes the person’s LinkedIn URL, which you can pass to the linkedin-to-person endpoint for a full profile.

### Does people search return email addresses?

No. Search returns names, titles, LinkedIn URLs, company fields and location. Get the work email with the name-domain-to-email endpoint.
